Admin
Joined: 09 Nov 2005
Posts: 7410
Location: Russia
|
 Posted: Mon Oct 27, 2008 7:55 pm Post subject: Hash Bruteforcing History Format |
 |
|
v0.1
For each record (i.e. for each completed and unsuccessful brute-force attack), the format provides 1.5 byte or, in the by-bit view: '0XXXXXXYYYYY', where XXXXXX – are the character sets used in the attack, and YYYYY – is the depth that has been reached by the attack (1 to 31 characters).
Character sets are encoded as follows:
| Code: | numeric: 000001
loweralpha: 000010
alpha: 000100
symbol14: 001000
symbol32: 010000
space: 100000 |
Character set combinations are formed obviously:
| Code: | loweralpha-numeric: 000011
alpha-loweralpha: 000110
alpha-loweralpha-numeric: 000111
And so on. |
Record examples:
02C (“000000101100”) = numeric, 12 characters
068 (“000001101000”) = loweralpha-numeric, 8 characters
1E6 (“000111100110”) = alpha-loweralpha-numeric-symbol14, 6 characters
And so on.
Multiple records in a same-hash history are to be separated with a period; for example, 02C.068 or 02C.068.1E6.
Ideas on the further development of the format:
- When the value of YYYYY = 00000, we could use the field XXXXXX for storing the id of the mask, which was used in the attack (for example, ?l?l?l?l?l?l?d?d?d?d) – i.e. we could also store information on mask attacks.
- The first bit of the record ‘1’ converts the record to the extended format – “10ZZZZZZZYYYYYYXXXXX”, which would allow us to use ZZZZZZZZ for storing the id of a non-Latin character set (Russian, German, French, etc.), which was used in the brute force attack), and the record with the first bits “11” will remain reserved.
You can encode or decode a hash history record here.
To discuss the format of hash history, please click here. |
|
