Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 28 Jul 2013 22:44:10 +0400
From: Solar Designer <>
Subject: Re: mask mode issues

On Sun, Jul 28, 2013 at 06:57:23PM +0200, magnum wrote:
> HashCat Built-in charsets
> ??? ?l = abcdefghijklmnopqrstuvwxyz
> ??? ?d = 0123456789
> ??? ?s = !???#$%&'()*+,-./:;????@[\]^_`{|}~

hashcat wiki has mangled this one, replacing what I think was the
double-quote character and the three characters less-than, equal, and
greater-than with some UTF-8 stuff.  Here's what I think what was meant,
represented via ASCII codes:

21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 3a
3b 3c 3d 3e 3f 40 5b 5c 5d 5e 5f 60 7b 7c 7d 7e

This is 32 chars.

> ??? ?a = ?l?u?d?s

This gives us 94 chars, so it's simply the whole range from 0x21 to 0x7e.
Note that it does not include the space character (0x20), which I think
was a bad idea.  Should we define our ?a to include the space character
as well?  (hashcat may then choose to redefine their ?a in a similar way
or not.)  Or should we use e.g. ?A to mean "really all printable ASCII,
including the space"?

> The "8 bit characters from ..." are poorly documented.

Yes, they are.  I think we can implement ?h, but initially omit the rest.

While German and French probably assume iso-8859-1, it is unclear to me
(without testing) which 8-bit charset is assumed for Russian, since
there are several of them in use.


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.