|
|||||||||||
|
Re: Identifying Win2K/XP Encrypted Files
From: Christopher Howell <howellc(at)njdcj.org>
Date: Thu Jan 30 2003 - 15:40:42 EST
Of course, this is only one minor victory. As many have brought out in related posts, there is much open to question regarding the cost/benefit of limited examination of a live system before blindly pulling the plug. Files encrypted using the Win OS is just one question. I have yet to come up with the ideal set and order of steps to take to keep every possible base covered. Whoever gets it first, please post it:) Thanks for everyone's comments. Chris.
Christopher Howell
>>> Craig Earnshaw <Craig.Earnshaw@TheEntrepreneur.com> 01/30/03 08:13AM >>>
The best scenario for dealing with the Windows 2000 encrypted file system (EFS) is to seize the machine, image it with you imaging tool of choice (Safeback, EnCase, dd etc etc) and then restore the image onto a blank drive, replace the drive in the original machine with you new copy of the drive, and then boot using a Linux boot disk developed by Peter Nordahl (I think his name is) available from http://home.eunet.no/~pnordahl/ntpasswd/. This can be used to change the logon passwords for the users of the machine, and let you log into their accounts (there are some caveats to this, but they're set out on the site so I'm not going to duplicate them here). Once you're logged into the accounts you are able to access all files stored within an EFS. Just my 2c - hope that it helps. Regards
Craig G Earnshaw
Christopher Howell wrote: This list is provided by the SecurityFocus ARIS analyzer service. For more information on this free incident handling, management and tracking system please see: http://aris.securityfocus.com Received on Thu Jan 30 21:59:29 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:01:43 EDT |
||||||||||
|
|||||||||||