Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 20 Dec 2012 11:03:39 -0500
From: Rich Rumble <>
Subject: Charset filters and options

I've searched all over, but can't exactly find the answer. If I want
to make rockyou.txt into my own chr file (I'm increasing from 8 to 12
length), and I use
--external=filter_alnum, it yields the following:

Successfully written charset file: alnum_12.chr (36 characters)

Should I modify the external filter to also include Uppercase letters?
It seems on the surface that only lower will be tried since it's a-z
0-9 (36).
I've made this modification but so far I can't tell (1hour) if it's
had an effect...
if ((c < 'a' || c > 'z') && (c < '0' || c > '9') && (c < 'A' || c > 'Z')) {
Naturally I've increased the CharCount to 62 after creating the chr file.
I assume incremental mode takes CASE into account, all.chr seems to
use uppercase characters, but the modified (the line above) doesn't
seem to even though the charcount went from 36 to 62 after recreating.
It's been discussed previously, but would it be possible to
"artifically" pad the pot file with at least one uppercase character
in each line so that incremental would be more likely to include an
uppercase in each try? Or should I use my all lower alpha_num to
stdout and use a mangling rule (NT) to make that happen. I'm sure I
could use all.chr and specify the external filter, but that seems like
it'd be slower than incremental "trained" to use at least 1 upper and
1 special or what have you.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.