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.




Network Security Nessus-Users
[Top] [All Lists]

Re: Windows Compliance Check Problems

Subject: Re: Windows Compliance Check Problems
Date: Thu, 25 Jan 2007 21:36:02 +0100

On Jan 25, 2007, at 8:37 PM, Mike Forrester wrote:

I'm hoping someone can figure out something that I'm missing when trying to get the Windows compliance checks working (UNIX works fine).


Policy file #2: federal_audit_microsoft_windows_os_guideline.audit

I get the following error in nessusd.dump every time I try to run a scan:

[26363](compliance_check.nbin:0x161a) A non-authenticated script attempted to use an authenticated function - returning NULL
[26363](compliance_check.nbin:0x161a) script_get_preference_file_location: script is not authenticated!

Try to set nasl_no_signature_check to 'yes' in nessusd.conf. Could you also send me the md5 you have of compliance_check.nbin ?



-- Renaud

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>