Re: [NSE] ssh2-enum-algos.nse

[Kris Katterjohn <katterjohn () gmail com>]

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

On 10/29/2010 12:16 AM, David Fifield wrote:
> On Tue, Oct 12, 2010 at 10:51:09PM -0500, Kris Katterjohn wrote:
> > 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?
>
> Wow, this script is really fast. Please commit.

Cool, I've committed it in r20844.

> David Fifield

Cheers,
Kris Katterjohn

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

iQIcBAEBAgAGBQJMyttkAAoJEEQxgFs5kUfu09MP/1bZ/ji7RWIJVDCayW4oWGRH
F5KW4uN2xiSouJtcMtDjO5P8/OqP/DbrETuxaCv9A6RyeiHEJkVD+BL/mPAtAUzp
sUDABezqUaTvoGm9sjs04SRLxIMEtFEvw14hVNRqtRh2rkv2+Y5eGS9rycIvvOhf
tIbyRHnHRsofBkEaTDmOvnQZOALM1bwGaBP3nwAAF19yrphyI1eVS/SFA8lJYWts
v7ykNeGO4X0ZMXZ+9kyL95jTt+tCfQO8QNzAEDehxFLCMgWpaXB4GWfvgvUcgUf3
vYikbNoRlTeK7QCdZ6S7P3drtnHC6aTDzueh0jEaT9G0FQ1T0cmQSsmXBlFjg1e5
C4bmEBh1AtgGRvHLp0cTfd6zdYjX9FCS7lUJSN61KjZ+Aeu9SHzO8q8MF1oaan+d
/vFnd4JXr++HRerghuxCDLQoRhkTYnmFG4BYGkC77OKvhG2dM5mCmdrCMn6UZfw8
pMaA2skJyY0DJoXitnAiWoFUOhEzvmqJzwtDcsxQnBIy9uLRZSbKTjMlWV7kRRQB
YCJwdJsTzr68mr9jGyObkjS06mMVNSvl8Gb+0CBnxWbz++BDUfhX69pyo0vndewB
hhLGIHf2d1A1uEZcqFnJwdQmNk2H01ffzcH7Q0qcWOjwhORN2OPO/kK4ZtchcF5h
LF3J8YqNYjgmIjW6RexG
=TNHb
-----END PGP SIGNATURE-----
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/