On Tue, Sep 23, 2003 at 01:10:59PM -0500, Terje Tollisen wrote: > I have installed nessus on a Linux (SuSE) box, and I�m trying to connect to it with > NessusWX. > I keep getting this error every time I connect: > �Server doesn�t have valid X.509 certificate� ... > I�m not sure if this is supposed to be the server as in the box where > nessud is running, or the certificate for the nessusd itself.
This is talking about the certificate for the Nessus daemon, which you created by running nessus-mkcert. > *Start up nessusd using �nessusd �p 995 �D�. Port 995 is chosen > because it is open through the F/W and allows ssl (I hope). > *Fire up NessusWX, and try connecting on port 995. This port is normally for POP3 over SSL. Using it shouldn't be a problem as long as you're not trying to run a POP server on that port, which doesn't seem to be the case here. > *I get the same error no matter which protocol I use. �Server doesn�t > have valid X.509 certificate� This error message means the server didn't send a certificate. Silly question.... did you restart your nessus server after running nessus-mkcert? You'll need to do that for Nessus to become aware of the certs and to use them. If you did, make sure you're using TLSv1 for the protocol (or whatever ssl_version is set to in your nessusd.conf). Does your nessusd.messages log file show anything interesting? And what happens if you use the nessus GUI / textmode client on the server machine itself? George -- [EMAIL PROTECTED]
pgp00000.pgp
Description: PGP signature
