I went ahead and changed the paranoia_level to 1 and launched and
accepted the cert locally. Hopefully this will fix it.
George A. Theall wrote:
On Fri, Sep 08, 2006 at 07:44:46AM -0400, Ian Marks wrote:
All my scanners run from cronjobs and they are firewalled to only
allow SSH to them so I can't see the cert from the GUI.
You might be able to get some idea of the problem by manually
connecting to nessusd via telnet or openssl's s_client command, but
you're best bet is to look at the logs. Can't you ssh in or get
console access? How do you do any system maintenance on the box?
> The reason I'm
thinking the cert expired is that 5 out of my 8 scanners were all
built at the same time and they are the ones that failed.
The error indicates the connection closed after the connection was
established. An expired certificate would result in an error
validating the certificate, if the client tries to do that (ie, see
the "-x" client option).
George
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
