mailing list archives
Re: [RFC] Username/Password NSE library
From: Kris Katterjohn <katterjohn () gmail com>
Date: Tue, 17 Jun 2008 17:10:04 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Brandon Enright wrote:
On Tue, 17 Jun 2008 15:46:09 -0500
Kris Katterjohn <katterjohn () gmail com> wrote:
I've started working on a username and password NSE library. This
library will separately hand out usernames and/or passwords to
scripts for use with brute forcing or whathaveyou.
I'll probably have one set of functions return a closure to return the
usernames or passwords one-at-a-time, and possibly another set of
functions to return the whole username or password table.
Username specific passwords would be _really_ nice.
I'm thinking for root the password list would be a few hundred long.
For other users the list would probably be something like:
These are interesting ideas, especially the overall user-specific passwords.
Now I need opinions on good username and password lists to ship and
use by default. There is an ordered password list shipped with John
the Ripper which has 3107 entries. The license pretty much says
we can distribute it if we give credit and also ship the license.
Are there any ideas on a better list?
It has been my experience, both from UCSD being on constant
password guessing the victim side, and me being on the audit our
passwords side that more passwords is _not_ better. If you don't guess
the password in the first hundred tries or so is is very unlikely that
continued guessing will help much.
Guessing passwords over the network is expensive and there is a
diminishing return. The value of trying an additional password is
roughly inversely proportional to the number you have already tried.
We've found that a list of the 1000 most commonly guessed passwords
performs almost no better than 500 but takes twice as long.
Interesting! I've never been a brute-forcer, so I had no idea what a good
number of guesses would be.
Of course, it is up to the script how many attempts they make: the library
will only provide them with the data. This library is specifically for giving
scripts usernames and passwords, so that's a good reason to have a whole bunch.
On one hand, I don't want Nmap's list to end up being too small because
somebody's script does want to do a lot of guessing; but, on the other hand,
if a user wants a massive list to use, they can always select their own.
What about a good username list?
Besides the obvious root, webadmin, guest, admin, test, mysql, web,
oracle, student, staff, etc we should only use first names.
Nearly 100% of the SSH brute force compromises we fall to are just
first-name usernames like:
you get the idea
Good idea. Maybe there can be an option given to the username function to
return only "administrator" usernames like root, admin, etc. But thinking
about it for a second, it wouldn't be easy to do just reading from a list.
Of course we could just have the administrator names at the top of the list,
which is probably best anyway.
Any other comments are appreciated.
I think the best way to gather the root list is to collect real-world
honeypot data. I have data I can provide and I'm sure hundreds of
others on this list also have data. We should probably cat * | sort |
uniq -c | sort -nr | head 500 to make our list.
That would be awesome, though the actual number of entries in the list is
Overall I think this is a very good idea, Kris. I look forward to the
Ah, if only I can take credit for good ideas. This, like many things I work
on, was handed to me from people in the Thinking Stuff Up Dept. ;)
It really should be cool when it's complete because bruteTelnet will be ported
to it and it should make the creation of other brute-force scripts a bit easier.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org