-
June 7th, 2006, 04:32 PM
#1
Junior Member
Easy question on Nessus 3.0.3
Please let me know if there are specialized newsgroups to discuss Nessus commands.
Here is my question:
I've installed and launched Nessus on Fedora 5.
Going through the Nessus documentation (www.tenablesecurity.com), I didn't figure out how to scan a certain range of IP addresses.
I did:
/sbin/service/sbin/nessusd start
[OK]
But from there I am lost on how to proceed with this. Please advise.
-
June 7th, 2006, 05:28 PM
#2
You might want to check out this tutorial by thehourse13.
understand that there are many ways to install and configure Nessus. This tutorial covers only one of them. This tutorial makes several assumptions:
1. You are competent with Windows, Linux and basic networking. If you don’t know how to use command line FTP for example, then this tutorial will be of no use to you.
2. You have 2 computers, one with a Windows and the other with Red Hat, both in good working order. It also assumes that you have at least one supported compiler such as GCC installed on your Red Hat Box.
3. This tutorial is written by me with no references or “borrowed” material. If something doesn’t work or something isn’t clear, yell at me because I am 100% responsible.
LINK
Cheers:
-
June 7th, 2006, 09:32 PM
#3
The easiest way to scan with Nessus is to use the NessusWX Win32 GUI client. Read over the tutorials. If you're still lost, lemme know.
--TH13
Our scars have the power to remind us that our past was real. -- Hannibal Lecter.
Talent is God given. Be humble. Fame is man-given. Be grateful. Conceit is self-given. Be careful. -- John Wooden
-
June 7th, 2006, 09:39 PM
#4
The tutorials will help a lot. One thing that isn't all that clear for folks not used to the Linux environment is that nessusd is a daemon. That is what you ran. It needs to be running for you to do anything else. Now you need to open a second terminal screen and run the scan, if that is what you want to do. Or, you can use the NessusWX client on a Windows Desktop.
-
June 8th, 2006, 02:31 PM
#5
After running the daemon just add nessus user by using command nessus-adduser and then start nessus client by typing something like nessus. It will then connect to the daemon locally and you can then start scanning after you login with the user you just added.
----------------------------------------------------------------------------------------------------------
"If I'd asked my customers what they wanted, they'd have said a faster horse." ~ Henry Ford
-
June 8th, 2006, 05:50 PM
#6
Junior Member
I installed the NessusWX client on Windows.
I launch the Nessus console, I do "Communications", Name=<IP address_Linux_Nessus_Server>.
Port number = 1241 (default)
Encryption=unencrypted.
Authentication
Login=admin password=mypassword
Then on the client I am getting
Error:Server doesn't support NTP/1.2 protocol. Connection terminated.
Any idea what I am missing here ? Is the NTP/1.2 the Network Time Protocol ? I am browsing through the "Help" files and it doesn't mention how to enable NTP on the Nessus server (Linux) software.
-
June 8th, 2006, 07:19 PM
#7
A few things here. Do you have OpenSSL on the linux box? At the console, openssl version
Is the Nessusd daemon running? At the console, netstat -an | grep 1241
--Th13
Our scars have the power to remind us that our past was real. -- Hannibal Lecter.
Talent is God given. Be humble. Fame is man-given. Be grateful. Conceit is self-given. Be careful. -- John Wooden
-
June 8th, 2006, 09:19 PM
#8
Junior Member
Yes, the nessus demo is running.
I started it by doing nessusd -D
#openssl version
returned
OpenSSL 0.9.8a 11 Oct 2005
netstat -an | 1241
returns
tcp 0 0 0.0.0.0:1241 0.0.0.:* LISTEN
Then from my nessuswx, if do "telnet <linux_nessus> 1241"
I am able to connect to the Linux box; and then netstat -an | 1241 lists an established connection OK.
The error "NTP/1.2 protocol. connection terminated" persists though.
-
June 12th, 2006, 11:32 PM
#9
Junior Member
Great. It was a messed up cert.
I recreated the cert, copied to the client and now I can connect. Thanks all for your help.
Just neet to sctart the scanning process now.
-
June 13th, 2006, 11:48 AM
#10
OK, but you did run through and did a mkcert the first time around? If you did and it created a bad cert, I'd like to know about it. I want to report it to the developer. There should be a different warning on the client side when this happens.
Are you running the WX client 1.4.5D from http://nessuswx.nessus.org?
Thanks.
--TH13
Our scars have the power to remind us that our past was real. -- Hannibal Lecter.
Talent is God given. Be humble. Fame is man-given. Be grateful. Conceit is self-given. Be careful. -- John Wooden
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|