I've solved the problem now!
I had been creating the certificates using nessus-mkcert-client. This was creating the client certificates and it said it was adding the users to nessus. However, it was not asking for rules details, or creating the file.
I looked at using nessus-adduser, but when you opt for the 'cert' option it was asking for details, but not creating a cert. However, it was placing the rules file in the right place.
If I do nessus-mkcert-client first, and then nessus-adduser, I get the error message because the user already exists, so it won't let me do anything.
If I do nessus-adduser, and then nessus-mkcert-client, it warns me that 'Certificate, key or Nessus DN file(s) already exist.' and asks me if I want to overwrite them! I did this, and it created the file, and I copied it to my machine and everything worked fine!!
Is it supposed to work that way?
Thanks, Joe
At 10:55 08/03/2003, Renaud Deraison wrote:
On Fri, Feb 28, 2003 at 03:51:21PM +0000, Joe Dauncey wrote: > However, when I try and do it with certificates I get an error from > NessusWX - > 'Invalid username or password supplied' > I also get: > 'Connecting to server x.x.x.x (port 1241) using TLSv1 encrypted > connection... > SSL connection using DES-CBC3-SHA > Using < NTP/1.2 > > ERROR: Invalid username or password supplied. Connection terminated.'
Make sure there is a /usr/local/var/nessus/users/<login>/auth/rules and /usr/local/var/nessus/users/<login>/auth/dname.
-- Renaud
Joe Dauncey PGP Key ID: 0xEAA034D4
*** I am not a lawyer and my opinions are my own ***
