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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Oct 2014 14:42:33 +0200
From: Krisztián Pintér <>
To: "" <>
Subject: Re: [PHC] Design Rationale and Security Analysis of PHC candidates

On Thu, Oct 2, 2014 at 1:56 PM, Dmitry Khovratovich
<> wrote:

> Assuming random ROM (this is important, collisions are easy if ROM can be
> partially chosen)

i claim that the content of ROM is irrelevant. you can not generate
collisions with it, since it can only affect the "rate" part of the
sponge, and not the "capacity". to my understanding, even if you are
in complete control of all the sponge input, you still can not find
collisions (let alone preimages).

this is a primary design principle of mine. i aim to entirely reuse
the security claims of keccak.

Powered by blists - more mailing lists