mailing list archives
Re: [NSE] SSL Fingerprint Matching
From: David Fifield <david () bamsoftware com>
Date: Tue, 22 Feb 2011 13:24:26 -0800
On Mon, Dec 20, 2010 at 09:37:47PM -0600, Mak Kolybabi wrote:
Attached is a script that connects to SSL services and checks if the host's
fingerprint is in a given list. Also attached is a list containing the 2011
fingerprints from Little Black Box 0.1. While I have used this list by default,
other lists such as the Debian blacklist could be used as well. Each fingerprint
is associated with a short message to state why it is in the list, or where it
If we had compression libraries available, including these lists of fingerprints
with Nmap would be easier.
Comments, concerns, criticism, and testing are appreciated.
I made a few changes and think this script is almost ready to be
committed. I've attached files with these changes:
* Renamed ssl-known_key.nse to ssl-known-key.nse.
* Renamed ssl-fingerprints.txt to ssl-fingerprints.
* Used the new shortport.ssl portrule.
* Increased some debug thresholds.
* Allowed comments and blank lines in ssl-fingerprints.
* Added attribution comments to ssl-fingerprints.
To save space, how about storing hashes in the database without colons
separating bytes? They can continue to be shown in output.
The output looks like this:
|_ssl-known-key: 00:28:E7:D4:9C:FA:4A:A5:98:4F:E4:97:EB:73:48:56:07:87:E4:96 is in the database with reason
Little Black Box 0.1.
Please change it to be
|_ssl-known-key: Found in Little Black Box 0.1 - http://code.google.com/p/littleblackbox/ (certificate hash:
This will give users a little more context if they don't know what the
script is for.
Related to that, it would be nice if the description string didn't have
to be repeated for hashes with the same description. Could the data file
be reworked into something like this:
[Little Black Box 0.1 - http://code.google.com/p/littleblackbox/]
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/