Re: [Cfrg] Introduction, and some concerns regarding draft-irtf-cfrg-argon2

"Scott Fluhrer (sfluhrer)" <sfluhrer@cisco.com> Mon, 27 April 2020 17:45 UTC

Return-Path: <sfluhrer@cisco.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 B79373A126F for <cfrg@ietfa.amsl.com>; Mon, 27 Apr 2020 10:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=E6Yjalrn; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=vsz+Noa9
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 hciFDDDHQT8I for <cfrg@ietfa.amsl.com>; Mon, 27 Apr 2020 10:45:26 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 924723A1270 for <cfrg@irtf.org>; Mon, 27 Apr 2020 10:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9944; q=dns/txt; s=iport; t=1588009526; x=1589219126; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Bt/+Qp8Q9aYdC/gr7LVcIFj/sRQfOLZyIVtnxsrrRhU=; b=E6YjalrnHdqjScBaM02jDw0ReyBvW5/rYdzbHyxcuZR+b9XFIWR8VaSW 6U/IJUnUGKuh1qOAoSMVKEgjWaUUf6OX8N5XBZWhrPpV3bRsAl136lFH8 txbNoh9EeBbrioDyn8TebgBwvsaW81t2+7hYCRACalw5JGxUfukuqhmlZ o=;
X-IPAS-Result: =?us-ascii?q?A0CADAC3Gade/4wNJK1mgQKBR4ElLyQtBWxYIAQLKgqHW?= =?us-ascii?q?wOKc06CEYEBkk6EYIJSA1QLAQEBDAEBLQIEAQGBUIJ0AoIoJDcGDgIDAQEBA?= =?us-ascii?q?wIDAQEBAQUBAQECAQUEbYVWDIVxAQEBAQMSGxMBASsBDA8CAQgRBAEBDSIyH?= =?us-ascii?q?QgCBAESCAwOgwWBfk0DLgGoPwKBOYhhdIE0gwABAQWFJBiCDgmBOIJjgkaHF?= =?us-ascii?q?BqBQT+BEUOBT0kHLj6EUINCgi2OQIkPJIo4j3sKgkWHHJEBY5wYj3qdBgIEA?= =?us-ascii?q?gQFAg4BAQWBaCOBVnAVO4JpUBgNlSaKVnQ1AgYIAQEDCXyNEAGBDwEB?=
IronPort-PHdr: =?us-ascii?q?9a23=3ArQNikRE3R/XS1s/P3+fn9p1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNV?= =?us-ascii?q?cejNkO2QkpAcqLE0r+eeXkazE6BslYfFRk5Hq8d0NSHZW2PgeAuHC54D8MFx?= =?us-ascii?q?m6LhJ7drinPInUgoz3z/q155DYfwRPgny6fK92KxK16w7Ws5teiop5IaF3wR?= =?us-ascii?q?zM6ndPdv8ew2R0bV6ehBfz4M6s8fsBuzxdofcg69JNXe3hcqI0QKYQDDM9L3?= =?us-ascii?q?t06Q=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.73,324,1583193600"; d="scan'208,217";a="457700970"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Apr 2020 17:45:25 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 03RHjP3O025550 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 27 Apr 2020 17:45:25 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 27 Apr 2020 12:45:25 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 27 Apr 2020 13:45:24 -0400
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 27 Apr 2020 12:45:24 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kh+UsbPoWUjkvSBDCjnXowkknirvhjdnWVeECxwmI6Y0WCtGEWYe9t5KeouMyrtbHKuTK+EkXdmd5QvIEsiVfS+Ak9L/+ChjJkniQVbmU8bKaOFlQuWRjt/P6F1nB10p3q2Mj/M60tzGmx8dnlPGmxP8Cl1SxXnwGk6LdOhFsa+aXaHL9LJrgSGzVySVorfoMsaph4FBY7nKWWJScfmRcn1lORzxC9/2uvoYtC8s+KRLkFkPzZSJ+QKHtoYTlvGaZPvtqsuyxfypE8j7qkCDTp9XUhj2uv/RBGjeXhQyfE1KqogWn41eugGS+JhbQJQYy6jFik2SuNJrF6XaAHi3Fg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9MH8X/YvJXoqFSh9u79tzrnGmRueAhy5qvtTpm2trM4=; b=UdPlyvZ2EIySm75tVEI2BUZ0bVyAz8D+LoRHor90cZdgp1bT3XxFcAXdj1gxsO3a2O53tB5uZZHjCJ+Jk8zJxvJN1y8qnQVIp4A05M7R7DTDQuaSAmKP3rACVU5gv7fL2KdliMIDSfpvFLCutSQM1IJVt/dTXFBc0L8JmlnXKHrtxmvzmdS7He5nbEmj/a28Am1eQ8bmBCjSs1C33jr+QTRDIt2CpwKM594MkuOVyu/zRc121K0sOKH6n7DYCBrWbTHHWp2T1ngz8hSgAPDahCTOR9pVNNEHlVosuRcu09lo72HY3aKqgKYe9cfRA5gieRorO3L/ie0auMhfquAYBQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9MH8X/YvJXoqFSh9u79tzrnGmRueAhy5qvtTpm2trM4=; b=vsz+Noa9i13QNS+o9QnlCPOsIxcpxGHLa7rVsSSl/xMS224VKaDco1FcU7RlDotbdU/2GxRk4NIBEMnU6+58w2uiWtuqJuHqQXoAce4r9Nf+pluEW0Y2xTkTi1U1fhX8oHQRfQxZxC3i3T8RS+ctnP81EWRQsYhyhCbp8fpcl1w=
Received: from MN2PR11MB3936.namprd11.prod.outlook.com (2603:10b6:208:13f::15) by MN2PR11MB3661.namprd11.prod.outlook.com (2603:10b6:208:f0::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2937.13; Mon, 27 Apr 2020 17:45:23 +0000
Received: from MN2PR11MB3936.namprd11.prod.outlook.com ([fe80::40a5:ee00:396d:b922]) by MN2PR11MB3936.namprd11.prod.outlook.com ([fe80::40a5:ee00:396d:b922%4]) with mapi id 15.20.2937.020; Mon, 27 Apr 2020 17:45:23 +0000
From: "Scott Fluhrer (sfluhrer)" <sfluhrer@cisco.com>
To: Gwynne Raskind <gwynne@darkrainfall.org>, "cfrg@irtf.org" <cfrg@irtf.org>
Thread-Topic: [Cfrg] Introduction, and some concerns regarding draft-irtf-cfrg-argon2
Thread-Index: AQHWG9BFmbACj+0lBUSa6nxX6XEs5qiNPONg
Date: Mon, 27 Apr 2020 17:45:23 +0000
Message-ID: <MN2PR11MB3936FD85BDABA7C36C97CFEFC1AF0@MN2PR11MB3936.namprd11.prod.outlook.com>
References: <56194F94-E5B1-4599-902D-CC74D1A4D729@darkrainfall.org>
In-Reply-To: <56194F94-E5B1-4599-902D-CC74D1A4D729@darkrainfall.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sfluhrer@cisco.com;
x-originating-ip: [173.38.117.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1196dc3a-f001-461d-355b-08d7ead2c319
x-ms-traffictypediagnostic: MN2PR11MB3661:
x-microsoft-antispam-prvs: <MN2PR11MB366192740FE93EBD44EA680DC1AF0@MN2PR11MB3661.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0386B406AA
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR11MB3936.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39860400002)(346002)(376002)(136003)(396003)(366004)(9686003)(55016002)(53546011)(33656002)(2906002)(26005)(71200400001)(81156014)(8676002)(6506007)(8936002)(478600001)(66446008)(76116006)(66476007)(110136005)(7696005)(66946007)(5660300002)(66556008)(316002)(86362001)(64756008)(186003)(52536014); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5zjxatK8oapPtVrCZpt5Rmw1O8XzV5WEkXM2JU4qqHniTIT+gY05uppShQ47A9Jn4h+VnG5S7DQe/XmomM5sKL2RvFaysnS7hvWqje/BNXeL+8FhV7dREuwpJRadmy8ANQRfOKsiARH5jBfZlJOlMiP/4cOrW98ERXMu558BKnZFLqCFeg06flf4n40IlyY5FDbmg3nT3pw1KFVsAyT9k6nTCQBHmSSakdsR/osbP//+PzmftEvZyHNtSBytiX4A6iBv7kVGjVG+0xXI9FJJyNF1adRBMLTAVE1THoZSwgUgXwc59AbhtLJCWt/YHGIdCX5QxoX/h2RH1sfHdjenvf3iCSg1yMlAiNGatGhgXXewC7wZkC/0dUeFxRbLAiyTCN57K2kKHO1VUW1MndGHXMZ/KOXfJxB7/2RPoduu2HVNg/kscGuwcHZ8gmtpL8VR
x-ms-exchange-antispam-messagedata: kWHXV6iOlPKtTng/ySTqZBh/Pqtqgk/e8/pqc60KGZ616AJwCE3iLzvUdCoBWGitEvg5aF4I8MEG/J6rTkZs0+aLUyzMY0wxzOMRrEEqpHuovBXv/sXW7f55re3hXk1tK9cH0HnO1Gg9GRXPFWL5GZnNE2u4lTmFW3GkPPY1AA1BfQutqByv/9uPu6ICBo1cm5i4DKycBDvMIeaSQBxVch/Bhb9eyRpUvNINKcs46zu31NXn2GqHiuVkX9+RrOHlym6C2RzmdkbYgz03CmUxDM9dQ//b2NnAKlsnL9YdnXTwf1fYzdekcHJXyTkSFqu7OSQ7gPTGlI0/wdU5NHTrt7bkpLMWgB6DTkCrLl13NQ/QcSLyoJeSIEzl9mnbO9Eze8zlRryzmTO5hyBFz5mLIJTyJcq7hhXcGXq2BEdJ6UzSdA84DRM1rYZ1hDtw4IspYr8/BoVu7c9JEhu2SUrfzsriaYVG/PRzp79fLTCPyPk+x7qaFPYTtJfQ0Isrgef239CNNBfdLtTy49hpQbbtQhsnfBxGk7P2X9l9lLsq3fVENbIXROw/8Mk1csonA1oChIFiDs+HQuSCZxIO0Ewwtwhea0rS8zB78C4VyXFG6KBzi78QyestbjBJlO+wiqSPWIxCH/ewsgy8YFlEqW3E1btg+3xzgjIDCNg9O1oG6+vM9ZOXrvIwnEKozBmOpXAhhB9gnRgZDQcuk9bI59PXymteEKsLokEHk3PloE+CFCL+vSh4CNFjkLS/LwwUaLuYOAlDw3HRYnPm9qAYbUFzG5n6sUlqsBrz5Jh3LQGWA1g=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB3936FD85BDABA7C36C97CFEFC1AF0MN2PR11MB3936namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1196dc3a-f001-461d-355b-08d7ead2c319
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Apr 2020 17:45:23.2855 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: SRtiUXT3B+2w/r+52/MF21MRKso5Uy7EJ5Xn8ebghfkSkEaD8Z4arpl304lzUhYCr6qQjOJz2puSHrF/fPZE2Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3661
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/BrC6MDwzG_YWmUv8S9KBeJJw3-c>
Subject: Re: [Cfrg] Introduction, and some concerns regarding draft-irtf-cfrg-argon2
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
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: Mon, 27 Apr 2020 17:45:30 -0000

I haven't seen any public responses, and so, while I'm not an editor of this particular draft, I'd like to reply to your concerns.

We would love to hear your critiques, both about minor errors such as typos, in addition to more major problems, such as ambiguities in the specification.

One major reason these drafts are published is to get them correct; by helping us make the draft better, you are helping us a great deal.

And, there isn't any secret handshakes to work on this mailing list; we welcome everyone.  And you are certainly not out of line.

I look forward to hearing your corrections and your suggestions.  Thank you.

From: Cfrg <cfrg-bounces@irtf.org> On Behalf Of Gwynne Raskind
Sent: Sunday, April 26, 2020 9:40 AM
To: cfrg@irtf.org
Subject: [Cfrg] Introduction, and some concerns regarding draft-irtf-cfrg-argon2

Hello!

My name is Gwynne Raskind; I'm a software engineer with a fairly wide range of technical experience and interests. I'm new to this mailing list, and to the IRTF in general - a colleague suggested that I subscribe to this working group's community to bring up an issue of concern to me with regards to the currently published draft of the specification of the Argon2 key derivation function (formally draft-irtf-cfrg-argon2-10).

In the course of both my work and general interest, I had occasion to investigate this algorithm and to attempt to build an implementation natively in the Swift language. Unfortunately, I found the draft in its present form to be less helpful than I had hoped. After a considerable amount of time spent studying the C reference implementation and comparing it with the specification, I was able to derive a nearly complete and partially functional implementation of my own. It was a fascinating learning experience, but I also noted a significant number of typographical errors, incomplete descriptions, missing elements, and other problems in the spec itself.

As I have an active interest in the cryptography space, as well as plenty of experience as both a technical writer and as a systems engineer, I took it upon myself to write up a somewhat exhaustive list of the various issues I encountered in the spec, ranging from technical analysis to grammatical concerns: I would be very pleased to contribute it (along with some accompanying suggestions of potential corrections) if it would be welcomed. I apologize if I'm in any way out of line; I couldn't find any kind of guidelines for how to approach this sort of problem, short of doing exactly this, so here I am.

Thanks for reading through this, and I hope to get the chance to help out!


-- Gwynne Raskind