Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: Remote host is not using the good version

Subject: Re: Remote host is not using the good version
Date: Sat, 17 Dec 2005 05:14:24 +0000
From: "George A. Theall" <theall@tenablesecurity.com>


On Fri, Dec 16, 2005 at 07:43:53PM +0000, Linuxnizer The Mesmorizer wrote:

>>   openssl s_client -connect $nessusd_host:1241 \
...
> Before and after give the same output:
> verify depth is 2
> gethostbyname failure
> connect:errno=0

Substitute the name of your nessusd host for '$nessusd_host' in the
commandline.

Sorry, should have known that. Here it is again:
verify depth is 2
CONNECTED(00000003)
depth=1 /C=US/L=Paris/O=Nessus Users United/OU=Certification Authority for localhost.localdomain/CN=localhost.localdomain/emailAddress=ca@localhost.localdomain
verify return:1
depth=0 /C=US/L=Paris/O=Nessus Users United/OU=Server certificate for localhost.localdomain/CN=localhost.localdomain/emailAddress=nessusd@localhost.localdomain
verify return:1
2848:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:s3_pkt.c:1052:SSL alert number 48
2848:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c:529:


The funny thing that it's working fine now. I mean connect->disconnect->reconnect without restarting NessusClient.

The only thing I did was copy a client cert & key from remote host with same username & password. I know this seems illogical. But that's the only thing I did beside rebooting my machine.

Linuxnizer

_________________________________________________________________
Are you using the latest version of MSN Messenger? Download MSN Messenger 7.5 today! http://messenger.msn.co.uk


_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>