phc-discussions - Re: [PHC] Submission deadline extension (March 31)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAOLP8p5LTLVxWdvu6g28sj9oy=GqckT9FvshBTSCnDJHZdks4g@mail.gmail.com>
Date: Mon, 6 Jan 2014 19:05:56 -0500
From: Bill Cox <waywardgeek@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Submission deadline extension (March 31)

Nice.  Here are parameter's I've added to NoelKDF:

num_threads     - the number of threads to run in parallel
parallelism     - number of inner loops allowed to run in parallel - should
match
                  user's machine for best protection
num_hash_rounds - number of SHA256 rounds to compute the intermediate key
clear_in        - when true, overwrite the in buffer with 0's early on

Also, I "borrowed" the excellent Catena idea for "garlic", and use t_cost
in the outer loop, where I double memory each time through the loop.  Users
wont need it, but server admins will like it.  I also have a flag like
yours for clearing and freeing memory.

I have to say that people on this forum have been extremely generous with
their ideas and feedback.  As a crypto noob, I've benefitted tremendously.

Now... as for your chart.  That looks like your telling me the password
length based on the runtime of the hash.  Is this right?  A snooper for
run-time is trivial and runs in user mode.

Bill

Content of type "text/html" skipped