[Cfrg] Review of draft-irtf-cfrg-argon2-03

Russ Housley <housley@vigilsec.com> Thu, 05 July 2018 16:51 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6A18130E6C for <cfrg@ietfa.amsl.com>; Thu, 5 Jul 2018 09:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBYGRQC34u7R for <cfrg@ietfa.amsl.com>; Thu, 5 Jul 2018 09:51:09 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36764130E19 for <cfrg@ietf.org>; Thu, 5 Jul 2018 09:51:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 1D288300A2A for <cfrg@ietf.org>; Thu, 5 Jul 2018 12:51:07 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id AEIr1THvt5Po for <cfrg@ietf.org>; Thu, 5 Jul 2018 12:51:06 -0400 (EDT)
Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 13703300445 for <cfrg@ietf.org>; Thu, 5 Jul 2018 12:51:06 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Message-Id: <C5D1534B-BCFF-4EB4-A982-40BB1CBAC469@vigilsec.com>
Date: Thu, 05 Jul 2018 12:51:06 -0400
To: cfrg@ietf.org
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/N1WH_bUyNunHc3Y6D-fDjZPcgIE>
Subject: [Cfrg] Review of draft-irtf-cfrg-argon2-03
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2018 16:51:11 -0000

ocument: draft-irtf-cfrg-argon2-03
Reviewer: Russ Housley
Review Date: 2018-07-06


The CFRG Chairs asked me to see if my comments on -02 were addressed.
Most of my comments were resolved.  See below.


Summary: Almost Ready


Major Concerns:

> Section 3.5: This section defines the compression function G.  It makes
> use of the BLAKE2b round function P, which is explained in Section 3.6.
> Section 3.6 defines another function G, which is different than the 
> compression function.  I realize that both G functions are discussed in
> other documents ([I-D.saarinen-blake2] and [ARGON2]), but there ought to
> be a way to avoid this name collision.

I did not see any changes to address this comment.

> Section 5: I tried to compile the code, and it does not work with gcc.
> Is there a missing include file?

The missing header file was provided.  However, the most obvious way of
putting these pieces together does not work.  First, if one puts all of
the files in one directory, they will not compile.  Second, if one puts
the blake2-related files in a subdirectory, the process gets further,
but there are still some errors.  I stopped investigating at this point.
I suspect specific compiler options are needed.  Please add some
instruction at the front of Section 5.


Nits:

> Section 1: s/implementer oriented/implementer-oriented/

This still needs to be corrected.

> Most of the document uses "=" for assignment, but Section 3.6 uses "<-".
> Please use "=" throughout.

Section 3.5 uses "->" and "<-".  Section 2 does not help me understand the
meaning.  If it is simply assignment, please use "=".


New Nit:

Section 9.2: s/[BZ17] also prove the/[BZ17] also proves the/