Hi,
The Nessus SSL plugin shows a completely incorrect cipher list. The
plugin calls OpenSSL's SSL_get_ciphers() function, which returns the
list of ciphers supported by *our* host, not the remote. This may
depend on the protocol version and/or OpenSSL settings, so it is not
always the same, though.
The list of ciphers supported by the remote end is not easily
available in SSLv3/TLSv1. The client sends a list of cipher suite
proposals in the "Client Hello" packet, and the server chooses one of
them. Thus, the only way to obtain the list of supported cipher suites
is to try all known suites one by one.
In SSLv2, this information is available (at least in theory),
because the Hello messages are different.
I have written a small Perl script which tries the known cipher suites
one by one; converting it to NASL shouldn't be a big problem...
Any volunteers? :-)
Best regards,
Pasi
--
Pasi Eronen E-mail pasi.eronen@nixu.com
Nixu Oy Tel +358 50 5123499
Mäkelänkatu 91, 00610 Helsinki Fax +358 9 4781030
The Nessus SSL plugin shows a completely incorrect cipher list. The
plugin calls OpenSSL's SSL_get_ciphers() function, which returns the
list of ciphers supported by *our* host, not the remote. This may
depend on the protocol version and/or OpenSSL settings, so it is not
always the same, though.
The list of ciphers supported by the remote end is not easily
available in SSLv3/TLSv1. The client sends a list of cipher suite
proposals in the "Client Hello" packet, and the server chooses one of
them. Thus, the only way to obtain the list of supported cipher suites
is to try all known suites one by one.
In SSLv2, this information is available (at least in theory),
because the Hello messages are different.
I have written a small Perl script which tries the known cipher suites
one by one; converting it to NASL shouldn't be a big problem...
Any volunteers? :-)
Best regards,
Pasi
--
Pasi Eronen E-mail pasi.eronen@nixu.com
Nixu Oy Tel +358 50 5123499
Mäkelänkatu 91, 00610 Helsinki Fax +358 9 4781030