On Wed, Jan 15, 2003 at 05:54:37PM +0100, Brian Ipsen wrote:

> My /etc/nessus/nerssusd.conf
...
> # Crypto options
> peks_username = nessusd
> peks_keylen = 1024
> peks_keyfile = /etc/nessus/nessusd.private-keys
> peks_usrkeys = /etc/nessus/nessusd.user-keys
> peks_pwdfail = 5

I believe these are obsolete but shouldn't affect your scans.

> # Added by nessus-mkcert
> #
> cert_file=/usr/com/nessus/CA/servercert.pem
> key_file=/var/nessus/CA/serverkey.pem
> ca_file=/usr/com/nessus/CA/cacert.pem

These look ok.

> But when trying to connect from my client I get:
> 
> Nessus Console [Version 1.4.2] Ready
> SSL library initialized
> Connecting to server w.x.y.z (port 1241) using SSLv3 encrypted connection...
> ERROR: Server doesn't have valid X.509 certificate
> 
> Any idea what the problem is - did I miss something in my configuration ??

According to the source for NessusWX, the server didn't return a cert. 
Does the nessusd logfile hold anything of interest? What happens if you
run "openssl s_client -connect w.x.y.z:1241 -ssl3"?

George
-- 
[EMAIL PROTECTED]

Attachment: msg03272/pgp00000.pgp
Description: PGP signature

Reply via email to