|
|||||||||||
|
RE: Identifying Win2K/XP Encrypted Files
From: George M. Garner Jr. <gmgarner(at)erols.com>
Date: Wed Feb 19 2003 - 11:15:58 EST
>> I suppose there are plenty of ways a Win2K/XP administrator can crash
Crashing a Windows system didn't used to be a problem. :-) [Un]fortunately, MS systems are becoming more reliable and you may need to use something like http://www.osr.com/files/BANG.zip. Note that bang installs a small service on the subject system and modifies the system registry. Use at your own risk.
One disadvantage of this method is that device drivers may register a
callback routine that is executed during and written to the crash dump.
See
Power management also has been suggested as a possible method for gathering volatile evidence from a running system. Power management is a cooperative process between the operating system and the applications running on a system, however. As such, it should be pretty easy to exploit or frustrate. There are a number of good methods for acquiring evidence from a running computer system. Each of these methods has its advantages and disadvantages. Each of these methods, including pulling the plug, involves some level of evidence reduction or loss. In all probability, each of these methods may be frustrated to some extent, particularly if your suspect knows in advance what you are going to do. The important thing is to understand the advantages and disadvantages of each method and then choose wisely based on what you are investigating and what you suspect. Regards, George. 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 Wed Feb 19 13:05:45 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:01:43 EDT |
||||||||||
|
|||||||||||