Re: [Cfrg] [MASSMAIL]Re: adopting Argon2 as a CFRG document

["Paterson, Kenny" <[e-mail]>]

Hi Paul, everyone,

I think there's general consensus here that we'd like the Argon2 team to
respond to the attacks as part of the CFRG process - and I am sure they'll
be doing so anyway for a wider audience. The chairs will reach out to the
team and find out what their plans are.

Regards

Kenny

On 28/01/2016 21:53, "Paul Grubbs" <[e-mail]> wrote:

>Would it be out of the question to ask the authors of Argon2 (or anybody,
>really) to do a more formal analysis of its space-hardness? It would be
>nice to have a proof (e.g. based on pebbling arguments) of some kind of
>time-space tradeoff for
> Argon2. 
>
>On Thu, Jan 28, 2016 at 3:39 PM, Grigory Marshalko
><[e-mail]> wrote:
>
>Indeed, the PHC competition has significantly contributed to the design
>and analysis of password-hashing schemes. It's a nice mixture of crypto
>and engineering. So it would be desirable to wait until we understand the
>limits of attacks and corresponding countermeasures.
>The article on baloon hashing is a significant step forward for
>understanding these issues.
>
>Regards,
>Grigory Marshalko,
>expert,
>Technical committee for standardisation "Cryptography and security
>mechanisms" (ТC 26)
>www.tc26.ru <http://www.tc26.ru>
>22 января 2016 г., 22:31, "Paterson, Kenny" <[e-mail]>
>написал:
>> Mike,
>>
>> Thanks. The authors of the Argon2 design may in due course tweak their
>> design to avoid the identified problems, or argue that they are not
>> sufficiently worrisome to warrant a change to the design.
>>
>> We definitely need to factor this in to our deliberations, and we will
>> take the time to do so. Let's see how it plays out...
>>
>> Regards
>>
>> Kenny
>>
>> On 22/01/2016 19:20, "Mike Hamburg" <[e-mail]> wrote:
>>
>>> We might want to hold off on Argon2 — at least on finalizing it — until
>>> the team has
>>> responded to (and hopefully mitigated) the issues mentioned at
>>> https://eprint.iacr.org/2016/027. Essentially the problem is that
>>>Argon2
>>> can be computed
>>> in less space than advertised. The team said that they are planning a
>>> response, cf
>>> 
>http://permalink.gmane.org/gmane.comp.security.phc/3606
><http://permalink.gmane.org/gmane.comp.security.phc/3606>
>>>
>>> Cheers,
>>> — Mike
>>>
>>> On Jan 22, 2016, at 11:10 AM, Paterson, Kenny
>>><[e-mail]>
>>> wrote:
>>>
>>> Dear CFRG,
>>>
>>> Having received limited feedback either way from the group
>>>(specifically,
>>> one voice in favour), the CFRG chairs have decided to adopt
>>> 
>https://tools.ietf.org/html/draft-josefsson-argon2-00
><https://tools.ietf.org/html/draft-josefsson-argon2-00> as a CFRG
>document.
>>>
>>> If you have objections or concerns, please reply to this email or
>>>directly
>>> to CFRG chairs.
>>>
>>> Sincerely,
>>>
>>> Kenny Paterson (for the chairs)
>>>
>>> On 06/11/2015 11:47, "Paterson, Kenny" <[e-mail]>
>>>wrote:
>>>
>>> Hi Stephen,
>>>
>>> Yes, the chairs are amenable to this. We've been keeping an eye on the
>>> password hashing competition and were planning a work item in this
>>>area.
>>>
>>> Any comments from the group, either supporting or objecting to us
>>>adopting
>>> this draft in the RG?
>>>
>>> Cheers,
>>>
>>> Kenny
>>>
>>> (for the chairs)
>>>
>>> On 06/11/2015 02:18, "Cfrg on behalf of Stephen Farrell"
>>> <[e-mail] on behalf of
>>> [e-mail]> wrote:
>>>
>>> The password hashing competition has a winner and some folks
>>> in the openpgp wg are interested in using that winner. I guess
>>> this might be better processed via cfrg if folks are amenable
>>> to that.
>>>
>>> Thanks,
>>> S.
>>>
>>> _______________________________________________
>>> Cfrg mailing list
>>> [e-mail]
>>> 
>https://www.irtf.org/mailman/listinfo/cfrg
><https://www.irtf.org/mailman/listinfo/cfrg>
>>
>> _______________________________________________
>> Cfrg mailing list
>> [e-mail]
>> 
>https://www.irtf.org/mailman/listinfo/cfrg
><https://www.irtf.org/mailman/listinfo/cfrg>
>
>_______________________________________________
>Cfrg mailing list
>[e-mail]
>https://www.irtf.org/mailman/listinfo/cfrg
>
>
>
>
>
>
>