![]() what credentials are you using? Have you verified that the relevant file has protection settings / ACLs that allow your user to access that file? On Windows, there is no such thing as 'user X can access everything' unless you've set that up beforehand.) It's also quite unclear what the mismatch is about: you say that one folder fails - but is it the folder, or files in the folder that fails? (In a live image, I'd expect no folder information to be retained, only file paths?) In such case, you should be able to identify a file - but you don't, and you don't say why.įor some reason you don't even identify or classify the relevant folder - why not? Is it a user folder? Is it a system folder? As what user are you doing the image (i.e. Switching to two other writeblockers seems not have no reason for it: one should be enough. You have a lot of information, but I can't see any conclusions about where the problem isn't. Irrelvant submissions will be pruned in an effort towards tidiness. Vote based on the quality of the content. Topics include digital forensics, incident response, malware analysis, and more. This subreddit is not limited to just the computers and encompasses all media that may also fall under digital forensics (e.g., cellphones, video, etc.). ![]() The field is the application of several information security principles and aims to provide for attribution and event reconstruction following forth from audit processes. A community dedicated towards the branch of forensic science encompassing the recovery and investigation of material found in digital devices, often in relation to computer crime.
0 Comments
Leave a Reply. |