Ethical Hacking Training at InfoSec Institute Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Workarounds for Windows Event File corruption |
|---|---|
| Date: | Mon, 10 Jan 2005 10:09:33 -0500 |
Use dumpevt to dump your event logs. Sonja L. Robinson, CISA Forensic Specialist, Digital Investigations HIP Information Security Group Tel: 212-806-4125 srobinson@hipusa.com -----Original Message----- From: Jeff Bryner [mailto:jbryner1@yahoo.com] Sent: Friday, January 07, 2005 1:15 PM To: forensics@securityfocus.com Subject: Workarounds for Windows Event File corruption I'm working on a case where I'd like to get time stamp info out of a windows application event log (AppEvent.evt). If I copy the file to another windows box and open it via event viewer I get the dreaded message about the file being corrupted. Web searches all lead to support articles suggesting deletion of the file to recover..obvioulsy not my solution. I can strings -el the file and get the descriptions of the events but I *really* want the time stamp associated with the entries. I've tried hex editing the file manually to match the header/footer to what I'm seeing in other working event log files, but I haven't found the right combination yet. Ideally I'd like to be able to open it on another windows box and capture screen prints of the events. Any clues from this group? Thanks, Jeff. ----------------------------------------------------------------- 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 CONFIDENTIALITY NOTICE: This e-mail transmission, including any attachments to it, may contain confidential information or protected health information subject to privacy regulations such as the Health Insurance Portability and Accountability Act of 1996 (HIPAA). This transmission is intended only for the use of the recipient(s) named above. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify me by reply e-mail and destroy the original transmission in its entirety without saving it in any manner. ----------------------------------------------------------------- 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
| Previous by Date: | Re: Workarounds for Windows Event File corruption, subscribe |
|---|---|
| Next by Date: | Re: Workarounds for Windows Event File corruption, Ansgar -59cobalt- Wiechers |
| Previous by Thread: | RE: Workarounds for Windows Event File corruption, Jerry Shenk |
| Next by Thread: | RE: Workarounds for Windows Event File corruption, Jeff Bryner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |