Ethical Hacking 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: Checking when the OS was first installed |
|---|---|
| Date: | Tue, 31 May 2005 10:39:29 +0200 |
On 2005-05-29 Lubrano di Ciccone, Christophe (DEF) wrote:
The date of the boot.ini file or the winnt folder (%systemroot%) may help you.
Maybe, but since it's the configuration file for the bootloader, it is prone to changes, so this seems very unreliable to me. Regards Ansgar Wiechers -- "All vulnerabilities deserve a public fear period prior to patches becoming available." --Jason Coombs on Bugtraq
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Resetting the root password (was: user name from security logs), Ansgar -59cobalt- Wiechers |
|---|---|
| Next by Date: | Re: aretzj.exe -- reappearing unknown system file, Michael Painter |
| Previous by Thread: | RE: Checking when the OS was first installed, Lubrano di Ciccone, Christophe (DEF) |
| Next by Thread: | Re: Checking when the OS was first installed, Hostas.lt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |