phc-discussions - Re: [PHC] omegacrypt and timing

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+hr98G94e2w2ueJ0dmXRnuDJuWg93ojBrSn-3ew9n4qs2H67Q@mail.gmail.com>
Date: Wed, 17 Sep 2014 11:53:32 +0200
From: Krisztián Pintér <pinterkr@...il.com>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] omegacrypt and timing

On Wed, Sep 17, 2014 at 11:30 AM, Bill Cox <waywardgeek@...hershed.org> wrote:
> However, AntCrypt, OmegaCrypt, and Schvrch all tried to introduce data
> based branching

i picked omegacrypt because i just spotted this. out of the 3,
antcrypt seems to be the worst, the other two can get away with some
blinding (dummy operations), but you can't compensate for differences
in floating point, as the timing is just unknown and depends on
zillions of factors, including the data itself.