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: problem with remote registry access |
|---|---|
| Date: | Thu, 23 Jun 2005 11:21:50 -0700 |
Registry access plugins require you to supply a username and password in your Nessus configuration. It is not possible to access internal details of a system without the correct credentials, otherwise, computers would be completely insecure. Robert -----Original Message----- From: nessus-bounces@list.nessus.org [mailto:nessus-bounces@list.nessus.org] On Behalf Of Matt Craig Sent: Thursday, June 23, 2005 9:24 AM To: nessus@list.nessus.org Subject: problem with remote registry access Running FreeBSD 5.3 University campus environment First off, I am a newbie with Nessus I am experimenting with implementing a Nessus scan with Netreg. I am using Net::Nessus::Scanlite. I want to scan a new student computer that has been connected to the network for vulnerabilities to curb the amount of dirty computers on the network. I have a working perl cgi on a web page that initiates a scan on the connecting computer, but for most Nessus plugins I have tried, I get log messages like this: Not launching smb_registry_full_access.nasl against 10.10.194.78 because the key SMB/registry_access is missing (this is not an error) This results in no holes found for machines I know to be dirty, since the nasl was not run to find the holes. After some reading, it is my current understanding that these nasls won't run because remote registry access is not configured on the machine being scanned. Am I correct? If I am correct, this could pose a problem, since I have no control on the setup and configuration of computers students bring on campus. If I can't scan student's computers with important plugins which just happen to need remote registry access, then the usefulness of this project would be severely diminished. Is there any way around this problem? I would appreciate any help or insight to this problem. Feel free to shoot me down over my newbiness. Thanks. _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | problem with remote registry access, Matt Craig |
|---|---|
| Next by Date: | RE: Scan Issue, Bilal Nasrallah |
| Previous by Thread: | problem with remote registry access, Matt Craig |
| Next by Thread: | 3com switches false positives, Jordan Wiens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |