Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 15 Aug 2015 20:49:06 +0800
From: Kai Zhao <>
Subject: Re: auditing our use of FMT_* flags

Hi magnum,

On Tue, Jul 28, 2015 at 2:30 AM, magnum <> wrote:
> On 2015-07-27 15:57, Kai Zhao wrote:
>>> $ ./john --test=0 --format=dominosec8
>>> Will run 8 OpenMP threads
>>> Testing: dominosec8, Lotus Notes/Domino 8 [8/64]... (8xOMP)
>>> FAILED (cmp_all(1))
>>> I did the same thing to those formats which do not set FMT_8_BIT
>>> and they are ok. Such as, descrypt, bsdicrypt, tripcode
>> Could you help me with the FMT_8_BIT ? Do I understand right ?
>> Thanks very much.
> I'm not sure about this but this problem seems to be similar to FMT_CASE
> (just a self-test-technical issue). So just like for FMT_CASE you should try
> testing with some input file and a wordlist instead.

Below is the test vectors of DOMINOSEC8_fmt_plug.c:

static struct fmt_tests tests[] = {
        {"(HsjFebq0Kh9kH7aAZYc7kY30mC30mC3KmC30mCluagXrvWKj1)", "hashcat"},

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 ? I think
I can not use the wordlist mode and write "hashca\xF4" directly to the
wordlist file.



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.