[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 15 Aug 2015 16:47:21 +0200
From: Frank Dittrich <frank.dittrich@...lbox.org>
To: john-dev@...ts.openwall.com
Subject: Re: auditing our use of FMT_* flags
On 08/15/2015 02:49 PM, Kai Zhao wrote:
> Below is the test vectors of DOMINOSEC8_fmt_plug.c:
>
> static struct fmt_tests tests[] = {
> {"(HsjFebq0Kh9kH7aAZYc7kY30mC30mC3KmC30mCluagXrvWKj1)", "hashcat"},
> {"(HosOQowHtnaYQqFo/XlScup0mC30mC3KmC30mCeACAxpjQN2u)",
> "pleaseletmein"},
> {NULL}
> };
>
> If I want to change the "hashcat" -> "hashca\xF4" which changes the last
> character. How can I test the "hashca\xF4" with some input files ?
As long as the hash and the password don't contain a few illegal
characters (for hash: tab and newline, for password: newline), you can
always use ./john --list=format-tests
$ for f in `./john --list=format-details --format=cpu|cut -f 1`; do
./john --list=format-tests --format=$f |cut -f 3 > hashes.$f; done
Warning: SAP-B format should never be UTF-8.
Use --target-encoding=iso-8859-1 or whatever is applicable.
Test scrypt 1: plaintext contains line feed
Test scrypt 1: ciphertext contains line feed or separator character ' '
Warning: SAP-B format should never be UTF-8.
Use --target-encoding=iso-8859-1 or whatever is applicable.
$ for f in `./john --list=format-details --format=cpu|cut -f 1`; do
./john --list=format-tests --format=$f |cut -f 4- > passwords$f; done
Warning: SAP-B format should never be UTF-8.
Use --target-encoding=iso-8859-1 or whatever is applicable.
Test scrypt 1: plaintext contains line feed
Test scrypt 1: ciphertext contains line feed or separator character ' '
Warning: SAP-B format should never be UTF-8.
Use --target-encoding=iso-8859-1 or whatever is applicable.
Frank
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.
