syskey verification of installation

Kore (KoreLAB.GAO.GOV)
Fri, 24 Sep 1999 17:42:14 -0400

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Peter da Silva: "Re: Alert: Microsoft Security Bulletin (MS99-038) - Source Routing Pa tch"
• Previous message: SBakerREEMAY.COM: "Re: What if you cannot trust your antivirus-software?"
• Next in thread: Gayler, David: "Re: syskey verification of installation"
• Reply: Gayler, David: "Re: syskey verification of installation"
• Reply: Iain Gair: "Re: syskey verification of installation"

In an attempt to verify the security parameters of several NT server
systems, I have been attempting to verify the status of syskey (whether it
has been applied or not). I have been unsuccessful to date. Of course if
you go to the console of each machine and run syskey.exe, a dialog box will
pop up showing the status but this is not a practical solution. I have
tried comparing the dates of files modified by syskey (winlogon.exe,
samsrv.dll, samlib.dll) to the dates of other key system files not modified
by the syskey installation, but this does not yield consistent results.

In order to verify NT servers conformity to corporate policy there must be
some good way to verify the status of syskey from a command line or small
script. ANY IDEAS?

CJ Warweg

• Next message: Peter da Silva: "Re: Alert: Microsoft Security Bulletin (MS99-038) - Source Routing Pa tch"
• Previous message: SBakerREEMAY.COM: "Re: What if you cannot trust your antivirus-software?"
• Next in thread: Gayler, David: "Re: syskey verification of installation"
• Reply: Gayler, David: "Re: syskey verification of installation"
• Reply: Iain Gair: "Re: syskey verification of installation"

This archive was generated by hypermail 2.0b3 on Fri Oct 01 1999 - 12:37:42 CDT