phc-discussions - Re: [PHC] Some Schvrch issues

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]

Date: Fri, 4 Apr 2014 08:27:04 +1000
From: Rade Vuckovac <rade.vuckovac@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Some Schvrch issues

Hi Daniel

It seems that parameter recommendations were not clearly stated in the
submission.
To reiterate:
password + salt + whatever < 1 Kbyte
Security is 256 bit therefore outlen is fixed to 4 meaning four u64bit
words.
Sorry if it was not clear enough.

Regards, Rade

On Thu, Apr 3, 2014 at 1:44 PM, Daniel Franke <dfoxfranke@...il.com> wrote:

> Some further issues:
>
> Lines 86 and 87 are buffer overflows if inlen + saltlen > 2048. Line 114
> is a buffer overflow if outlen > 2048. There are no checks for these
> conditions.
>
> When t_cost = m_cost = 0 and outlen = 2048, the only irreversible
> operation performed is discarding the final value of 'carry' in the
> stir() function. This makes Schvrch vulnerable to a straightforward 2^64
> preimage attack when these settings are used.
>

Content of type "text/html" skipped