If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

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.

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.

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.

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.