From: "George A. Theall" <theall@tenablesecurity.com>
On Fri, Dec 16, 2005 at 08:43:04AM +0000, Linuxnizer The Mesmorizer wrote:
> There is an improvement, after generating a new certificate
Which certificate did you re-generate? If you generated a new server
cert, you will need to regenerate the client certs too as the CA cert
has changed.
I just regenerated the client cert only.
> I was able
> to connect and scan local machine. However, when I disconnect and try to
> reconnect again I get the (SSL error). Here is more details from the
> command line.
>
> [1686] SSL_connect: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
This error typically occurs when a client doesn't have access to the CA
cert used to sign the server's cert. trusted_ca in the client and
ca_file in the server both use the same filename, and if the client
couldn't read the file I'd expect a completely different error. So if
you're still getting this and the client is on a separate machine from
the server, make sure you copy the CA cert file from the nessusd host to
the client host.
That's strange, since I can connect the first time, but not when I
disconnect and try to reconnect again.
George
--
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
_________________________________________________________________
Be the first to hear what's new at MSN - sign up to our free newsletters!
http://www.msn.co.uk/newsletters
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
