[NSE] ssh2-enum-algos.nse

[Kris Katterjohn <katterjohn () gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey everyone,

I've attached a pretty simple script which connects to a SSH2 server and
reports on the algorithms offered.  If verbosity is set, then the actual list
of algorithms is printed; otherwise, just a count of the offered algorithms
are given.

When the "client to server" and "server to client" lists are identical for a
type (the order specifies preference), then they are printed only once as a
combined type.

If you look at the script @output, you can see it looks similar to the output
of ssl-enum-ciphers.nse.

To test, you need to use SVN trunk r20601 or later.  In this revision I
changed ssh2.lua's kex_init() parameters which my script depends on.

Any comments or reasons not to commit?

Cheers,
Kris Katterjohn


P.S. I have the following comment in the script before sending the kex packet:

"I would think that the server would send its kex data right after
receiving and verifying our protocol id string above, then we could
just use it here, but I've seen no definitive documentation saying
that we don't ever send ours first.  All I've seen is that if the
server doesn't care about compatibility with older clients then it
MAY send its kex data after the protocol id string.  So I guess I'll
send it here until I know for sure (removing this send works against
OpenSSH though)."

Any ideas on this?  Ithilgore, if you're reading this: did you run across
anything definitive working on the SSH module for Ncrack?  Did I misinterpret
the RFC or is it just vague?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJMtSytAAoJEEQxgFs5kUfufI8QAJdpTN6ZNKw0RwEETzaE0mPy
dffVynJNZ4zGu94N+SHzgJBaZxJ1BiJQOqMr5oZFSgs6x5RGuAkXZZEi+VeebUwL
ZLCrOnNoJ3vIu21lj52jRZDNN56KNyKaufk8D9uAdMBYEoH9KxjzqgE4Xt7Z9riq
uFGPLsqHJ+OxOol7p5S9A14C+hzld6xBXreCvEYjNl7zvXMYqG/9XFRSSYKi8vbY
aXIzWpJjhKAKmnNwTaTpHLy4/Zu+mhy3cE5jMUYwQsVAQ+H7DqzHC8l05+D5kF3X
QpDwLRMmOzaZRCMuiONbRc2xuNaJHnNFGczRpgJEav4FR3CpbpCIErmu85zmE8SO
JMIMf6iZlFtq50WAEhDoK9SYtl0xbBV7ukE/0BnK/KxfMdfrgucEXnmO0y4BeLB2
Fu3v3gJqWTWB+V1Zw/5M8mvN1Z6pH2JmZBhqn2ZZGOGPiE6DE6Zm36vHZROP8a3A
6S8MFViYIAaOeJ9rmb5d/I6WywJbRMiLTz4/s1sINQMsd0B5D0Y7EdVonCpOpjyG
Y4d9EvOGw2SvpoTGjz3Prj3ls9lzFqzoJmA+mTa1Sisf/tNCzKdLrZgz0ZZ1/0x8
ZHe48JGrgfO5QsDWSCSF8qpdhnVvq47rcKO43bsYfy/vC1VAWprzkHficz+CuRux
aEBvh2tsNDI7YBo5tb7b
=BvU7
-----END PGP SIGNATURE-----

Attachment: ssh2-enum-algos.nse
Description:

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/