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] [thread-next>] [day] [month] [year] [list]
Date: Tue, 30 Sep 2014 14:09:47 +0200
From: Krisztián Pintér <>
To: "" <>
Subject: Re: [PHC] Design Rationale and Security Analysis of PHC candidates

On Tue, Sep 30, 2014 at 1:59 PM, Dmitry Khovratovich
<> wrote:
> It applies to the schemes that may leak secret information via timing
> side-channels.

in this case, i would refer to gambit documentation page 4 "notes on security"

The design obeys the recommendations of Crypto Coding Standard, specifically:

✓ Avoid branchings controlled by secret data

✓ Avoid table look­ups indexed by secret data

✓ Avoid secret­ dependent loop bounds

what would you consider needed to classify as "explored"?

Powered by blists - more mailing lists