From nobody Thu Aug 1 10:20:32 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B211201B4; Thu, 1 Aug 2019 10:20:29 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Alissa Cooper via Datatracker To: "The IESG" Cc: draft-ietf-curdle-gss-keyex-sha2@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migault@ericsson.com, curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.99.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Alissa Cooper Message-ID: <156468002959.19179.1501364206084512034.idtracker@ietfa.amsl.com> Date: Thu, 01 Aug 2019 10:20:29 -0700 Archived-At: Subject: [Curdle] Alissa Cooper's No Objection on draft-ietf-curdle-gss-keyex-sha2-10: (with COMMENT) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2019 17:20:30 -0000 Alissa Cooper has entered the following ballot position for draft-ietf-curdle-gss-keyex-sha2-10: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-curdle-gss-keyex-sha2/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for addressing my DISCUSS. From nobody Thu Aug 1 12:51:09 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34F331201BC; Thu, 1 Aug 2019 12:51:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 isC7VGWCTtR2; Thu, 1 Aug 2019 12:51:06 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BEB61201B4; Thu, 1 Aug 2019 12:51:06 -0700 (PDT) Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x71JooKE012622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 1 Aug 2019 15:50:53 -0400 Date: Thu, 1 Aug 2019 14:50:50 -0500 From: Benjamin Kaduk To: Ron Frederick Cc: denis bider , Loganaden Velvindron , "draft-ietf-curdle-ssh-ed25519-ed448.all@ietf.org" , Daniel Migault , "curdle@ietf.org" , bjh21@bjh21.me.uk Message-ID: <20190801195049.GB1006@kduck.mit.edu> References: <20190604174029.GC8678@prolepsis.kaduk.org> <20190607222610.GH83686@kduck.mit.edu> <20190730213418.GQ47715@kduck.mit.edu> <7103DFAE-92F8-4727-8F8E-3CE33E18B540@timeheart.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7103DFAE-92F8-4727-8F8E-3CE33E18B540@timeheart.net> User-Agent: Mutt/1.10.1 (2018-07-13) Archived-At: Subject: Re: [Curdle] new AD review comments on draft-ietf-curdle-ssh-ed25519-ed448-08 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2019 19:51:08 -0000 On Wed, Jul 31, 2019 at 09:27:59PM -0700, Ron Frederick wrote: > On Jul 31, 2019, at 4:19 PM, denis bider wrote: > > > I would suggest standards track given that ed25519 > > > is already public key is already implemented by OpenSSH. > > > > Just to confirm, there are other implementations too. > > > > For example, Ed25519 was introduced in Bitvise SSH Server and SSH Client in versions 7.21 (released end of 2016): > > > > https://www.bitvise.com/ssh-server-version-history-7 > > AsyncSSH also has implementations of both ssh-ed25519 (in version 1.0.0 from April 2015) and ssh-ed448 (in version 1.16.0 from March 2019). See https://asyncssh.readthedocs.io/en/latest/changes.html for details. I tested the AsyncSSH ssh-ed448 support against the Erlang SSH library, which supports both ssh-ed25519 and ssh-ed448. Other implementations of ssh-ed25519 are listed at https://ssh-comparison.quendi.de/comparison/hostkey.html. Thanks for the additional notes about implementation status! -Ben From nobody Fri Aug 2 08:20:15 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6843E120422; Fri, 2 Aug 2019 08:20:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= To: "The IESG" Cc: draft-ietf-curdle-ssh-ed25519-ed448@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migaultf@ericsson.com, curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.99.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= Message-ID: <156475920734.16394.8987359389003753752.idtracker@ietfa.amsl.com> Date: Fri, 02 Aug 2019 08:20:07 -0700 Archived-At: Subject: [Curdle] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draf?= =?utf-8?q?t-ietf-curdle-ssh-ed25519-ed448-09=3A_=28with_COMMENT=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2019 15:20:08 -0000 Mirja Kühlewind has entered the following ballot position for draft-ietf-curdle-ssh-ed25519-ed448-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I think this document should update RFC4253. From nobody Sat Aug 3 14:50:14 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DD4B1120143; Sat, 3 Aug 2019 14:50:11 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.99.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: curdle@ietf.org Message-ID: <156486901181.6232.10972341509486960100@ietfa.amsl.com> Date: Sat, 03 Aug 2019 14:50:11 -0700 Archived-At: Subject: [Curdle] I-D Action: draft-ietf-curdle-ssh-curves-09.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Aug 2019 21:50:12 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CURves, Deprecating and a Little more Encryption WG of the IETF. Title : Secure Shell (SSH) Key Exchange Method using Curve25519 and Curve448 Authors : Aris Adamantiadis Simon Josefsson Mark D. Baushke Filename : draft-ietf-curdle-ssh-curves-09.txt Pages : 6 Date : 2019-08-03 Abstract: This document describes the conventions for using Curve25519 and Curve448 key exchange methods in the Secure Shell (SSH) protocol. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-curdle-ssh-curves-09 https://datatracker.ietf.org/doc/html/draft-ietf-curdle-ssh-curves-09 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-ssh-curves-09 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sat Aug 3 14:52:47 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79140120134; Sat, 3 Aug 2019 14:52:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net 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 zUsRfVH_F-EN; Sat, 3 Aug 2019 14:52:43 -0700 (PDT) Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF2EB120143; Sat, 3 Aug 2019 14:52:43 -0700 (PDT) Received: from pps.filterd (m0108158.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x73Lqd8g011198; Sat, 3 Aug 2019 14:52:39 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=9MhI97unftVMMESNyn3I4WLqMZJ3LsZsdelCj3LdamA=; b=RUk+53a7ZXEHGJC36Ep6iKTDWqbeQ1P6dMVv9eBJ9OYbyyNT69PI7BsEPKZh142xpomb D8UnDv3xGsQQeCBREo7F5OqVEhLJa1hzCmQsywDkUJ5sIvxay91ON0WF2kd4f6PWrOHy FiT5Wf5YXY9IqJ8NOiDoCbkEYJWyweFtLs8eVZNXx5VGa1gxntW4b4fN6Liu9dZqSkza m+k/rP5/RsSUO4B9Yjfm+Y0SYQsOg4rKCaJA9nB5jsdU93K2XOBmkoX1V9Hz8K58wYbt p1UcV8QXcws9sAWQ3CH099l/b+BRSlESnc0smMsgP+ix5kexQMThdq98/weGGOHqQsCc Cg== Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp2051.outbound.protection.outlook.com [104.47.42.51]) by mx0a-00273201.pphosted.com with ESMTP id 2u55yq0rge-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 03 Aug 2019 14:52:39 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jnvh2gn8wpjoI93hdViXSVTiP1NUlOAOloVwCRWN7S7mneNkiLtUqKfkjQ+UBcWSteqzCB5pEB6uJdZUpxSQ8NtC6XTllNHEnR3IY6wB97oduNwCgwf7bPHtsTmfzGZB20ECzveUHjn4PNKzTL9sY2HDCvFRZiTVtRpbiBktyOYf7v9xyIOK+N4wcj5j3b40TWJk+YZaRvnfucqDKS+2BgoyQfXYaNiIMjdSU6IgLX4hZ31kPgoo165eO32BUgd084TaTwjQclPeHdVgqrvrYpxbTvTgNZKhcxF6ApKByBzXFEZO1mgpe8Kd56UWF+sm3LDlgDJLuugUKdaFDGvYsQ== 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=9MhI97unftVMMESNyn3I4WLqMZJ3LsZsdelCj3LdamA=; b=OY8AKyISRitVUlMPYRl5ISC7Ecx5vQ9YlGq2bW7lxNdOuXU7GQnEcwURwK1KiloJMURSXObxATjk3+B3hqIwfecy1Ar7Ti81HlpiB47LvmbNHzY8bqndbVTK1b0kJJNyccfSXH5PcDI36xColZD3WjzaKQjUk1OcP3Z7i1cr/R7w7ElF/5CmYu0l0c8jOdd3IfuuwoNhIG/UwPtO2JEn171xQYGFy65PSlBXKajSs24IJ9V4kS+jGyD5FT5zm3RdaiCUQZvTQjEMo0w9KoiiNlg1RCg+4GpKwKiweQTOQ6RqFVsIKTvFAZJmOTwREFZ9dddxjJp6WROwJCPvAkuZrg== ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=juniper.net;dmarc=pass action=none header.from=juniper.net;dkim=pass header.d=juniper.net;arc=none Received: from BYAPR05MB6182.namprd05.prod.outlook.com (20.178.55.87) by BYAPR05MB5814.namprd05.prod.outlook.com (20.178.49.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.9; Sat, 3 Aug 2019 21:52:36 +0000 Received: from BYAPR05MB6182.namprd05.prod.outlook.com ([fe80::1104:bda:d098:9be5]) by BYAPR05MB6182.namprd05.prod.outlook.com ([fe80::1104:bda:d098:9be5%7]) with mapi id 15.20.2157.011; Sat, 3 Aug 2019 21:52:36 +0000 From: Mark Baushke To: Daniel Migault CC: Benjamin Kaduk , curdle , "draft-ietf-curdle-ssh-curves.all@ietf.org" Thread-Topic: [Curdle] Second AD Review: draft-ietf-curdle-ssh-curves. Thread-Index: AQHUm9ZvRREIxp8iYketO0a/EGuBk6blCPcAgAAKJwCAAA34AIAACikAgAYolwA= Date: Sat, 3 Aug 2019 21:52:36 +0000 Message-ID: <0D4BB5A9-5E34-4038-BD5B-1EE63A67447D@juniper.net> References: <20190730214702.GS47715@kduck.mit.edu> <31257.1564525402@contrail-ubm16-mdb.svec1.juniper.net> <20190730231321.GU47715@kduck.mit.edu> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: ad328c71-763d-410b-8135-08d7185ce59a x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:BYAPR05MB5814; x-ms-traffictypediagnostic: BYAPR05MB5814: x-ld-processed: bea78b3c-4cdb-4130-854a-1d193232e5f4,ExtAddr x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:3968; x-forefront-prvs: 0118CD8765 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(39860400002)(366004)(346002)(376002)(136003)(189003)(199004)(26005)(6486002)(186003)(11346002)(446003)(476003)(2616005)(229853002)(6916009)(6436002)(36756003)(305945005)(7736002)(66476007)(66556008)(64756008)(66446008)(76116006)(66946007)(8936002)(8676002)(66066001)(81156014)(81166006)(5660300002)(478600001)(486006)(14454004)(68736007)(99286004)(558084003)(33656002)(6512007)(256004)(2906002)(102836004)(54906003)(3846002)(6116002)(4326008)(6246003)(316002)(6506007)(25786009)(53936002)(71190400001)(71200400001)(86362001)(76176011); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB5814; H:BYAPR05MB6182.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: +IBNdG7mFHrUG7VXkpaSMnTOH0TI0fXotp9XVkE9t52H6uAzBH2isvwiOcNIGiZ4Gw0uI8fuqX1HrXSBGd0cFVfzmq0ILYk7rXifYKMTk8XYF7O2tgairIWLDAdZ7eRUre/+Dkut4iNpSTZsEpkdxRT7usASzR/ascmnXi0KIJk5Wu5gExZqAoqYI8RrOc1YP0kfUwuKEp3Om2OvEeGFtkL65/CNXEnnwuiMdx6Shar6vJ9Xc3PJY4uup3h4lU9MYg7kFr4WGiWcu3e5snLs+qofkanm7a2j70O54Y4q5wXmF/Ox7TTPZQYfVfIumGwETD/FZ8WXUtrmzdbgq0DnRr0IfvgO0TQ/NJjZ2Z4axT++a3cbnEl4IynBsNeehNkP+z8zIUYJcmpD29dk6L2sanmbpd8WN+oR6Kywpx9PWxo= Content-Type: text/plain; charset="us-ascii" Content-ID: <3360F04DAB65C54D8E2C3F49FC28FB85@namprd05.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-Network-Message-Id: ad328c71-763d-410b-8135-08d7185ce59a X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Aug 2019 21:52:36.1622 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: uQ3DNe7XcAnf6keuBlBn5B+Ogyl29mLhQUaCdszD/N4gCfX9dSTGfLxjhBRTvYQc X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB5814 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-03_12:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=755 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908030259 Archived-At: Subject: Re: [Curdle] Second AD Review: draft-ietf-curdle-ssh-curves. X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Aug 2019 21:52:46 -0000 Hi Daniel, I have updated and uploaded the draft. Please let me know of any issues. -- Mark From nobody Sun Aug 4 09:51:57 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F4B712003F for ; Sun, 4 Aug 2019 09:51:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=timeheart.net 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 OfrND253A3Nc for ; Sun, 4 Aug 2019 09:51:53 -0700 (PDT) Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64FCC120033 for ; Sun, 4 Aug 2019 09:51:53 -0700 (PDT) Received: by mail-pl1-x62b.google.com with SMTP id 4so28501424pld.10 for ; Sun, 04 Aug 2019 09:51:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timeheart.net; s=mail; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=AzXjdpnnMnTzG6a6/+az5eCiVmjwsaUhJRF1roreKW8=; b=aSBTj/vwjTLH/V59hk3nvkpKgVzCNlilFUrjbZBpWrXGwP4HqXtlg/gr1lSUXP4Fq4 f9iOZfwNDtwv1QHDMkZ9jSaZiJqzrs0lEg2lSjcZAtx52Yte154fy9/nO/gMWBEn8qLZ ArIjQ5PX8Cv9QAUnrDI8KpgKgsAb4UFzll1t8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=AzXjdpnnMnTzG6a6/+az5eCiVmjwsaUhJRF1roreKW8=; b=LNvIku7k46702eBKTOtj4Imk+e2DPTgjrdNQY91YwbXtMpPfCcNuFkteuOS9zUtpQO f75YYa7Yl0r5WkDRo8UkTNF+7MiEDhGCDLZsNjxXJ6eIVSAgm62UWBKMW7NXVHQDIzNw uC2v3+/8VA8GAsxQ9izHqMxykiFOEyfoGb+YHYA6DQfK0JLaPOgdHuMHiKL3KWEmrwF9 T5jd4A2wbeK3EDBkdqiVpMSTusf3KW1CJ1rMugKKQoL+ey+RRFEEVs4liIa43gRHDEXJ DW9CsTFwu89aLUnzfcW4AXGJ4exWRzxNs6o/76CkMB/vW2+Esu+ckq1LKYLwbStozPKP yndw== X-Gm-Message-State: APjAAAV49V6oHACafhiAY4nIid4fLRH0waUI8cGLpAhXKn9we2t88IqT 8fQo4Xy/7DRpLOcG/jBNgEMRcQYL3SY= X-Google-Smtp-Source: APXvYqwK7HNPCXDzTomjrBclfwXSqwEHkf8TP7/XUdfPWFd2+3FWRfnmTOoq8oekP8jGBKmLCQasWg== X-Received: by 2002:a17:902:9a42:: with SMTP id x2mr142129324plv.106.1564937512696; Sun, 04 Aug 2019 09:51:52 -0700 (PDT) Received: from connect.timeheart.net.0.4.a.f.8.1.4.2.0.3.3.0.6.2.ip6.arpa ([2603:3024:18fa:4000::2]) by smtp.gmail.com with ESMTPSA id y128sm101439202pgy.41.2019.08.04.09.51.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Aug 2019 09:51:52 -0700 (PDT) From: Ron Frederick Message-Id: <7859169F-D86B-4027-B060-6BAA6FD6CA6A@timeheart.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_2B89F6A1-D496-47A0-8F3B-C1E7769F80A2" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Sun, 4 Aug 2019 09:51:51 -0700 In-Reply-To: <0D4BB5A9-5E34-4038-BD5B-1EE63A67447D@juniper.net> Cc: curdle To: Mark Baushke References: <20190730214702.GS47715@kduck.mit.edu> <31257.1564525402@contrail-ubm16-mdb.svec1.juniper.net> <20190730231321.GU47715@kduck.mit.edu> <0D4BB5A9-5E34-4038-BD5B-1EE63A67447D@juniper.net> X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [Curdle] Second AD Review: draft-ietf-curdle-ssh-curves. X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2019 16:51:56 -0000 --Apple-Mail=_2B89F6A1-D496-47A0-8F3B-C1E7769F80A2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Mark, On Aug 3, 2019, at 2:52 PM, Mark Baushke = wrote: > I have updated and uploaded the draft. Please let me know of any = issues. Here are a few thoughts on version 9 of the draft: In section 3, you say =E2=80=9CKey-agreement schemes Curve25519 and = Curve448=E2=80=9D, but these algorithms are not key-agreement schemes by = themselves. I=E2=80=99d recommend going with the proposed SSH names here = if you are discussing the full key agreement scheme and not the = underlying elliptic curve algorithms. In other words, I=E2=80=99d = suggest =E2=80=9CKey-agreement schemes curve25519-sha256 and = curve448-sha512=E2=80=9D (possibly with quotes around each), as done = earlier in this section. When detecting the all-zeroes value, the new text says it should = =E2=80=9Cabort if so, as described in Section 6=E2=80=9D of RFC 7748. = However, the original RFC doesn=E2=80=99t actually define what = =E2=80=9Cabort=E2=80=9D means. It says =E2=80=9Cabort if so (see = below)=E2=80=9D, but I don=E2=80=99t know what that is referring to. The = only mention of =E2=80=9Cabort=E2=80=9D is in sections 6.1 and 6.2, and = nothing in section 7 seems to really expand on what should be done if = the all-zeroes check matches. This is more a fault of RFC 7748 than it = is of this doc, but since you are now recommending to =E2=80=9Cabort=E2=80= =9D in this doc, it would be good to be more specific about what that = means for an SSH client/server. I=E2=80=99m also not sure the sentence about =E2=80=9CAlternative = implementations=E2=80=9D of these functions. There isn=E2=80=99t a lot = of clarity on how one would determine in an alternate implementation = when =E2=80=9Ceither input forces the shared secret to one of a small = set of values=E2=80=9D. Since this point is covered already in RFC 7748 = and this doc says =E2=80=9CNo further validation is required beyond what = is discusses in RFC 7748=E2=80=9D, though, I think it might be better to = just leave this out. --=20 Ron Frederick ronf@timeheart.net --Apple-Mail=_2B89F6A1-D496-47A0-8F3B-C1E7769F80A2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = Mark,

On Aug 3, 2019, at = 2:52 PM, Mark Baushke <mdb=3D40juniper.net@dmarc.ietf.org> wrote:
I have updated and = uploaded the draft. Please let me know of any issues.

Here = are a few thoughts on version 9 of the draft:

  • In section 3, you say =E2=80=9CKey-agreement schemes = Curve25519 and Curve448=E2=80=9D, but these algorithms are not = key-agreement schemes by themselves. I=E2=80=99d recommend going with = the proposed SSH names here if you are discussing the full key agreement = scheme and not the underlying elliptic curve algorithms. In other words, = I=E2=80=99d suggest =E2=80=9CKey-agreement schemes curve25519-sha256 and = curve448-sha512=E2=80=9D (possibly with quotes around each), as done = earlier in this section.
  • When detecting the = all-zeroes value, the new text says it should =E2=80=9Cabort if so, as = described in Section 6=E2=80=9D of RFC 7748. However, the original RFC = doesn=E2=80=99t actually define what =E2=80=9Cabort=E2=80=9D means. It = says =E2=80=9Cabort if so (see below)=E2=80=9D, but I don=E2=80=99t know = what that is referring to. The only mention of =E2=80=9Cabort=E2=80=9D = is in sections 6.1 and 6.2, and nothing in section 7 seems to really = expand on what should be done if the all-zeroes check matches. This is = more a fault of RFC 7748 than it is of this doc, but since you are now = recommending to =E2=80=9Cabort=E2=80=9D in this doc, it would be good to = be more specific about what that means for an SSH client/server.
  • I=E2=80=99m also not sure the sentence about =E2=80=9CAlternati= ve implementations=E2=80=9D of these functions. There isn=E2=80=99t a = lot of clarity on how one would determine in an alternate implementation = when =E2=80=9Ceither input forces the shared secret to one of a small = set of values=E2=80=9D. Since this point is covered already in RFC 7748 = and this doc says =E2=80=9CNo further validation is required beyond what = is discusses in RFC 7748=E2=80=9D, though, I think it might be better to = just leave this out.
-- 
Ron Frederick
ronf@timeheart.net



= --Apple-Mail=_2B89F6A1-D496-47A0-8F3B-C1E7769F80A2-- From nobody Tue Aug 6 07:39:19 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B79E120226; Tue, 6 Aug 2019 07:39:10 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: Roman Danyliw via Datatracker To: "The IESG" Cc: draft-ietf-curdle-ssh-ed25519-ed448@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migaultf@ericsson.com, curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Roman Danyliw Message-ID: <156510234996.19222.8394663725844648268.idtracker@ietfa.amsl.com> Date: Tue, 06 Aug 2019 07:39:09 -0700 Archived-At: Subject: [Curdle] Roman Danyliw's No Objection on draft-ietf-curdle-ssh-ed25519-ed448-09: (with COMMENT) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 14:39:17 -0000 Roman Danyliw has entered the following ballot position for draft-ietf-curdle-ssh-ed25519-ed448-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- A few editorial nits: ** References in Section 3 – 7, 10 to [RFC4251], [RFC4253] and [RFC8032] are showing up in the format “[RFC#], Section x.x [RFC#]”. For example, “[RFC4253], Section 6.6 [RFC4253]”. It should likely only be “Section x.x [RFC#]”. ** Section 8. Typo. s/the the/the/ ** Section 8. Typo and making it be “an example”, not “the example”. s/the SSHFP Resource Record for the Ed448 public key with SHA-256 fingerprint would be example be /The SSHFP Resource Record for a Ed448 public key with a SHA-256 fingerprint would, for example, be/ From nobody Tue Aug 6 10:32:45 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC58120275; Tue, 6 Aug 2019 10:32:37 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Alissa Cooper via Datatracker To: "The IESG" Cc: draft-ietf-curdle-ssh-ed25519-ed448@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migaultf@ericsson.com, curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Alissa Cooper Message-ID: <156511275710.18148.4644218386043433986.idtracker@ietfa.amsl.com> Date: Tue, 06 Aug 2019 10:32:37 -0700 Archived-At: Subject: [Curdle] Alissa Cooper's No Objection on draft-ietf-curdle-ssh-ed25519-ed448-09: (with COMMENT) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 17:32:38 -0000 Alissa Cooper has entered the following ballot position for draft-ietf-curdle-ssh-ed25519-ed448-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- It would be nice if this document briefly noted somewhere what the security properties are of Ed25519 and Ed448, or otherwise give some indication for why supporting these algorithms is a good thing. In Section 2.1, please use the RFC 8174 boilerplate. From nobody Tue Aug 6 10:38:52 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95A2B1205DD; Tue, 6 Aug 2019 10:38:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=k9jm3nxP; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ha+vOqZf 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 lq6lz2iYkEqw; Tue, 6 Aug 2019 10:38:42 -0700 (PDT) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7A321202CD; Tue, 6 Aug 2019 10:38:42 -0700 (PDT) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 8AAF6371; Tue, 6 Aug 2019 13:38:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 06 Aug 2019 13:38:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=4 9OChY71iFNKr1RHTxAYN0ALvwsqfCG16KfzE2YrOgc=; b=k9jm3nxPWDQ42Qqu/ kM5PGqEpC34i+xt9ENI5cTR8jvLPy3H1cWov1zYpA+wUlLeIwCRy7TzXMDoRu3Hy ED/VbQLS0UOdnn9uzMq0d4QoRjpnBCF8aX080cib86pgD69yMv66TIjyWB2YJMx3 XptLra8YOPPbX0N8kFGOfl84WyOj61UQ+YFEjkdtjcBOoAYklgNzv+Vds7Yy5fSc N2s5JrK5sbC1tFLmNOYQk5dUUi7V/LDtHJqM+RyptoPusafmovquvKq6tw3DUO5u 0ilinKXM6S4478sw3yHfstDlGkJIS5SjtDGRWB+GtWl8NFNayjUzplaGtXVUtbfI 4QIyQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=49OChY71iFNKr1RHTxAYN0ALvwsqfCG16KfzE2YrO gc=; b=ha+vOqZf7KgkNPpqVcGkTH13e6GgI1hx4LN03ClhSzfqd3gu4lIa6zoqB sCNXJoRMuljvndZ3s0ibDgaCjjRJrBx3iDibgpVh84A8MxNGTjVAMfeyO0zmwBag 9ht2XlXt30KF2L/XcVtMiEFXWwiHVjFGFYKxb/p/tf/1aESgwb2MkNxlqWBUC1MN 9wkFdXSmW+lo0tw2YxQ6McdjhgA/S7hVh/Lb2T7+QOJU3mPfTw/ZT7qgSwRq4L2P z1Zz8n2j998eceO/igU50qLdzFhQiABXxnnL+ssh/7an/zIFP8bc+MlrOJOaX1XA OKNv+WdDqE47na0V++MpqqINBCS4A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddruddutddguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhi shhsrgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomh grihhnpehivghtfhdrohhrghenucfkphepuddtkedrhedurddutddurdelkeenucfrrghr rghmpehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhush htvghrufhiiigvpedt X-ME-Proxy: Received: from alcoop-m-c46z.fios-router.home (pool-108-51-101-98.washdc.fios.verizon.net [108.51.101.98]) by mail.messagingengine.com (Postfix) with ESMTPA id 0BD0F80060; Tue, 6 Aug 2019 13:38:40 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Alissa Cooper In-Reply-To: <154683304030.17040.15801682371972802372@ietfa.amsl.com> Date: Tue, 6 Aug 2019 13:38:39 -0400 Cc: gen-art@ietf.org, draft-ietf-curdle-ssh-ed25519-ed448.all@ietf.org, curdle@ietf.org, ietf@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <2CF7F4F9-A85F-48D5-B469-57D7DCA14C8D@cooperw.in> References: <154683304030.17040.15801682371972802372@ietfa.amsl.com> To: Linda Dunbar X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Curdle] [Gen-art] Genart last call review of draft-ietf-curdle-ssh-ed25519-ed448-07 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 17:38:45 -0000 Linda, thanks for your review. The IANA registries into which this = document makes new registrations follow the IETF Review policy, which = requires an RFC published in the IETF stream. Arguably it could have = been informational but I don=E2=80=99t see a down side to publishing it = on the standards track. I entered a No Objection ballot. Alissa > On Jan 6, 2019, at 10:50 PM, Linda Dunbar = wrote: >=20 > Reviewer: Linda Dunbar > Review result: Ready with Issues >=20 > I am the assigned Gen-ART reviewer for this draft. The General Area > Review Team (Gen-ART) reviews all IETF documents being processed > by the IESG for the IETF Chair. Please treat these comments just > like any other last call comments. >=20 > For more information, please see the FAQ at >=20 > . >=20 > Document: draft-ietf-curdle-ssh-ed25519-ed448-?? > Reviewer: Linda Dunbar > Review Date: 2019-01-06 > IETF LC End Date: 2019-01-04 > IESG Telechat date: Not scheduled for a telechat >=20 > Summary: >=20 > This document proposes two names for public key algorithms (which are = specified > by other RFCs): ssh-ed25519 & ssh-ed448 >=20 > Major issues: >=20 > There is no "Standard" being specified by this document. The document = has a few > sentences to explain "public key algorithm for use with SSH in = accordance with > RFC4253, RFC4251" and give a name. and One sentence to say "Signatures = are > generated according to the procedure in RFC8032". >=20 > I don't understand why it is "Standard Track" document, non do I = understand why > it is a WG document. Does it take a whole WG to come out with a name = for an > algorithm specified in an RFC? >=20 > Minor issues: >=20 > Nits/editorial comments: >=20 > Linda Dunbar >=20 > _______________________________________________ > Gen-art mailing list > Gen-art@ietf.org > https://www.ietf.org/mailman/listinfo/gen-art From nobody Tue Aug 6 11:11:40 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14488120653; Tue, 6 Aug 2019 11:11:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com 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 8h310xboPQ_I; Tue, 6 Aug 2019 11:11:30 -0700 (PDT) Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-eopbgr810095.outbound.protection.outlook.com [40.107.81.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A20B9120666; Tue, 6 Aug 2019 11:11:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DLdjsJuqO0/XwT3GSpBS5YaE1eFk+LqBPJEcd6WIqFp3ViDoFQt+3dvRiSpdshNbXGBZ1CIgnO24w8pA0ZX71OHTYrsgkgqgOkAS1sUpqvWNtUHTdEhuGiX8YhT7pP5C6hSio38Ot6RcpSrjzQszBgZfQmAw98rslu50JUDiHMjGkHtE+RtazTJ7z4IPdWL+bPcr4wv0q74nKiixNjAKfDLnWYveOtQalxdSrU3NoRS948EJ12aW1SLgJx04dXtKyzF/24cl0UVQDvmaVi9xmFSrVet43Y2s554MIMw83u6XO7d4fpWY3yk2U7NkKFev4pmUOZHIJaW0Rk4nQJiNGw== 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=ekjsX9V7xoUoOZ3w8iSq60LY7SCYkAmrwwAOjr7KBuE=; b=KPRuFuxQAf4bv7eWDe4Py+HepwO4qwvxlYCwCjdvDDbkJ676A+PfnrJgSJ4c1X5xI8qrgEDn03WZwT/4bdhyoLrxZ6cKuGZAJOOX+NJZzXPDugU3airK93kR3d6+HboKdQrjO8q7kwojACFQxyH7OU4KLd/n3wFBF6C3JFvfCwqpt+yieQmqOLqgvaHsBrpUPFgOV2KBg4mLq1UBnZ+ypfLh6mwA7rx8YZIeptphEvSnSxt4uIMLDkY6V+ssFKifdi8eCgtvYQWLtGj6Jje04QdAcFQJn4YSmwgWd+cSpdetW2skboa3Qwt34PQUjKx3RP7XdCrktjR7aeXrwe3bAQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ekjsX9V7xoUoOZ3w8iSq60LY7SCYkAmrwwAOjr7KBuE=; b=AmeA6NArMdmOmHq37U7tAFsfAtJBQoJZCxZQONAPhkin4o5kDDf8wxHO8DDplINSgRB1WZajkOEojUo5tNJ5Ciwb5pCAvBSpDekqGNBmZbHRkuHKfbsEctvqPEipv9PnvjU6C72gToui7gWRIUhlVxlwoMuUn5OFq8UGQTgMWIc= Received: from MN2PR13MB3582.namprd13.prod.outlook.com (10.255.238.139) by MN2PR13MB3711.namprd13.prod.outlook.com (10.186.145.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.8; Tue, 6 Aug 2019 18:11:28 +0000 Received: from MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::51ed:57ae:d3a7:e4bd]) by MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::51ed:57ae:d3a7:e4bd%7]) with mapi id 15.20.2157.011; Tue, 6 Aug 2019 18:11:28 +0000 From: Linda Dunbar To: Alissa Cooper , Linda Dunbar CC: "draft-ietf-curdle-ssh-ed25519-ed448.all@ietf.org" , "gen-art@ietf.org" , "curdle@ietf.org" , "ietf@ietf.org" Thread-Topic: [Gen-art] Genart last call review of draft-ietf-curdle-ssh-ed25519-ed448-07 Thread-Index: AQHVTH3Po0xgQ+lZhU+c3IE4/7HPn6bua7PQ Date: Tue, 6 Aug 2019 18:11:28 +0000 Message-ID: References: <154683304030.17040.15801682371972802372@ietfa.amsl.com> <2CF7F4F9-A85F-48D5-B469-57D7DCA14C8D@cooperw.in> In-Reply-To: <2CF7F4F9-A85F-48D5-B469-57D7DCA14C8D@cooperw.in> 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=linda.dunbar@futurewei.com; x-originating-ip: [12.111.81.80] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 4b6cf1a4-d0a8-48e1-2da5-08d71a998063 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB3711; x-ms-traffictypediagnostic: MN2PR13MB3711: x-ms-exchange-purlcount: 3 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 0121F24F22 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(366004)(396003)(39850400004)(136003)(376002)(13464003)(189003)(199004)(53936002)(6306002)(6436002)(316002)(68736007)(54906003)(55016002)(110136005)(6506007)(53546011)(33656002)(6246003)(102836004)(11346002)(446003)(229853002)(44832011)(81166006)(26005)(81156014)(8676002)(476003)(9686003)(8936002)(7736002)(76176011)(305945005)(7696005)(99286004)(486006)(76116006)(74316002)(186003)(66066001)(14454004)(66476007)(66556008)(64756008)(66446008)(71200400001)(66946007)(71190400001)(6116002)(2906002)(45080400002)(478600001)(966005)(3846002)(25786009)(86362001)(5660300002)(4326008)(52536014)(256004); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3711; H:MN2PR13MB3582.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: Z9rPAgXy1mlWpPAz4v+d5cRGzDBcbJBzFkvYCXkhG0vlrjlf5qDbpMIeD8CM2H29+e2/zJZIno5YhA3vUwSUDXsG3kvqDelGIxewZt873ft7BFeXrIU3EiNVpHDp3NiRpTgI2WBhFGb/+TYk0G5MsAPho3LA3gxaYOB61azwPLv7rkii6px338rSraPhBhphjFJ/kjeG1KYE3vV3/bm2xmXizmlHtGO4SC3ULLNT/vFBdbeqNPZ9emT4lATFgDPZ0i++wpfmpxleelTCE9fvAg4GHlJHKsZ62ud6o9L0+TB2bMhW7bxcrjVnNu4Nh3D1WF0ovbUGZcTRouWR6hFSMu86PCD1GXxpziOCTGicnvZTSt63t5mEOZZcr4SG4hCJ/fZ5R5fvRrqLQGWiB7OqlckgZ94lvAteg5i3XpfX1Wc= x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: Futurewei.com X-MS-Exchange-CrossTenant-Network-Message-Id: 4b6cf1a4-d0a8-48e1-2da5-08d71a998063 X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Aug 2019 18:11:28.1097 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: nriB5L2jIsJ52NhhoCsPQg6xbTssOdn7nrRINfTYKhWn+KQtoEpFJS7egR4SzLYc6kVy46JWJt0Oh53yAt/Vjg== X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3711 Archived-At: Subject: Re: [Curdle] [Gen-art] Genart last call review of draft-ietf-curdle-ssh-ed25519-ed448-07 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 18:11:33 -0000 T2theS4gDQoNCkxpbmRhDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBHZW4t YXJ0IDxnZW4tYXJ0LWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBBbGlzc2EgQ29vcGVy DQpTZW50OiBUdWVzZGF5LCBBdWd1c3QgMDYsIDIwMTkgMTI6MzkgUE0NClRvOiBMaW5kYSBEdW5i YXIgPGxpbmRhLmR1bmJhckBodWF3ZWkuY29tPg0KQ2M6IGRyYWZ0LWlldGYtY3VyZGxlLXNzaC1l ZDI1NTE5LWVkNDQ4LmFsbEBpZXRmLm9yZzsgZ2VuLWFydEBpZXRmLm9yZzsgY3VyZGxlQGlldGYu b3JnOyBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0dlbi1hcnRdIEdlbmFydCBsYXN0IGNh bGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtY3VyZGxlLXNzaC1lZDI1NTE5LWVkNDQ4LTA3DQoNCkxp bmRhLCB0aGFua3MgZm9yIHlvdXIgcmV2aWV3LiBUaGUgSUFOQSByZWdpc3RyaWVzIGludG8gd2hp Y2ggdGhpcyBkb2N1bWVudCBtYWtlcyBuZXcgcmVnaXN0cmF0aW9ucyBmb2xsb3cgdGhlIElFVEYg UmV2aWV3IHBvbGljeSwgd2hpY2ggcmVxdWlyZXMgYW4gUkZDIHB1Ymxpc2hlZCBpbiB0aGUgSUVU RiBzdHJlYW0uIEFyZ3VhYmx5IGl0IGNvdWxkIGhhdmUgYmVlbiBpbmZvcm1hdGlvbmFsIGJ1dCBJ IGRvbuKAmXQgc2VlIGEgZG93biBzaWRlIHRvIHB1Ymxpc2hpbmcgaXQgb24gdGhlIHN0YW5kYXJk cyB0cmFjay4NCg0KSSBlbnRlcmVkIGEgTm8gT2JqZWN0aW9uIGJhbGxvdC4NCg0KQWxpc3NhDQoN Cj4gT24gSmFuIDYsIDIwMTksIGF0IDEwOjUwIFBNLCBMaW5kYSBEdW5iYXIgPGxpbmRhLmR1bmJh ckBodWF3ZWkuY29tPiB3cm90ZToNCj4gDQo+IFJldmlld2VyOiBMaW5kYSBEdW5iYXINCj4gUmV2 aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBJc3N1ZXMNCj4gDQo+IEkgYW0gdGhlIGFzc2lnbmVkIEdl bi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWEgDQo+IFJldmll dyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNz ZWQgYnkgDQo+IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVz ZSBjb21tZW50cyBqdXN0IGxpa2UgDQo+IGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+ IA0KPiBGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+IA0KPiA8 aHR0cHM6Ly9uYW0wMy5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBz JTNBJTJGJTJGdHJhYy5pZXRmLm9yZyUyRnRyYWMlMkZnZW4lMkZ3aWtpJTJGR2VuQXJ0ZmFxJmFt cDtkYXRhPTAyJTdDMDElN0NsaW5kYS5kdW5iYXIlNDBmdXR1cmV3ZWkuY29tJTdDOTg0NjVhNWFj ZWM3NGIxZWZiMTcwOGQ3MWE5NGYwNWQlN0MwZmVlOGZmMmEzYjI0MDE4OWM3NTNhMWQ1NTkxZmVk YyU3QzElN0MwJTdDNjM3MDA3MDk5MzEzMjk5MTU0JmFtcDtzZGF0YT1lSXNqQzduWDlsJTJGaVpB ZVRFWVZWNTY3RndtekUxUGVvaEdzY282enQ3alUlM0QmYW1wO3Jlc2VydmVkPTA+Lg0KPiANCj4g RG9jdW1lbnQ6IGRyYWZ0LWlldGYtY3VyZGxlLXNzaC1lZDI1NTE5LWVkNDQ4LT8/DQo+IFJldmll d2VyOiBMaW5kYSBEdW5iYXINCj4gUmV2aWV3IERhdGU6IDIwMTktMDEtMDYNCj4gSUVURiBMQyBF bmQgRGF0ZTogMjAxOS0wMS0wNA0KPiBJRVNHIFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVsZWQg Zm9yIGEgdGVsZWNoYXQNCj4gDQo+IFN1bW1hcnk6DQo+IA0KPiBUaGlzIGRvY3VtZW50IHByb3Bv c2VzIHR3byBuYW1lcyBmb3IgcHVibGljIGtleSBhbGdvcml0aG1zICh3aGljaCBhcmUgDQo+IHNw ZWNpZmllZCBieSBvdGhlciBSRkNzKTogc3NoLWVkMjU1MTkgJiBzc2gtZWQ0NDgNCj4gDQo+IE1h am9yIGlzc3VlczoNCj4gDQo+IFRoZXJlIGlzIG5vICJTdGFuZGFyZCIgYmVpbmcgc3BlY2lmaWVk IGJ5IHRoaXMgZG9jdW1lbnQuIFRoZSBkb2N1bWVudCANCj4gaGFzIGEgZmV3IHNlbnRlbmNlcyB0 byBleHBsYWluICJwdWJsaWMga2V5IGFsZ29yaXRobSBmb3IgdXNlIHdpdGggU1NIIA0KPiBpbiBh Y2NvcmRhbmNlIHdpdGggUkZDNDI1MywgUkZDNDI1MSIgYW5kIGdpdmUgYSBuYW1lLiBhbmQgT25l IHNlbnRlbmNlIA0KPiB0byBzYXkgIlNpZ25hdHVyZXMgYXJlIGdlbmVyYXRlZCBhY2NvcmRpbmcg dG8gdGhlIHByb2NlZHVyZSBpbiBSRkM4MDMyIi4NCj4gDQo+IEkgZG9uJ3QgdW5kZXJzdGFuZCB3 aHkgaXQgaXMgIlN0YW5kYXJkIFRyYWNrIiBkb2N1bWVudCwgbm9uIGRvIEkgDQo+IHVuZGVyc3Rh bmQgd2h5IGl0IGlzIGEgV0cgZG9jdW1lbnQuIERvZXMgaXQgdGFrZSBhIHdob2xlIFdHIHRvIGNv bWUgDQo+IG91dCB3aXRoIGEgbmFtZSBmb3IgYW4gYWxnb3JpdGhtIHNwZWNpZmllZCBpbiBhbiBS RkM/DQo+IA0KPiBNaW5vciBpc3N1ZXM6DQo+IA0KPiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoN Cj4gDQo+IExpbmRhIER1bmJhcg0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18NCj4gR2VuLWFydCBtYWlsaW5nIGxpc3QNCj4gR2VuLWFydEBpZXRm Lm9yZw0KPiBodHRwczovL25hbTAzLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91 cmw9aHR0cHMlM0ElMkYlMkZ3d3cuDQo+IGlldGYub3JnJTJGbWFpbG1hbiUyRmxpc3RpbmZvJTJG Z2VuLWFydCZhbXA7ZGF0YT0wMiU3QzAxJTdDbGluZGEuZHVuYmENCj4gciU0MGZ1dHVyZXdlaS5j b20lN0M5ODQ2NWE1YWNlYzc0YjFlZmIxNzA4ZDcxYTk0ZjA1ZCU3QzBmZWU4ZmYyYTNiMjQwMQ0K PiA4OWM3NTNhMWQ1NTkxZmVkYyU3QzElN0MwJTdDNjM3MDA3MDk5MzEzMzA5MTUxJmFtcDtzZGF0 YT1nJTJCcWcwRWRYV2lFDQo+IHZRYzVpU2ZqOWp6MWdzVENTWXFNJTJGT3V3RE03STRzM2slM0Qm YW1wO3Jlc2VydmVkPTANCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18NCkdlbi1hcnQgbWFpbGluZyBsaXN0DQpHZW4tYXJ0QGlldGYub3JnDQpodHRwczov L25hbTAzLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0ElMkYl MkZ3d3cuaWV0Zi5vcmclMkZtYWlsbWFuJTJGbGlzdGluZm8lMkZnZW4tYXJ0JmFtcDtkYXRhPTAy JTdDMDElN0NsaW5kYS5kdW5iYXIlNDBmdXR1cmV3ZWkuY29tJTdDOTg0NjVhNWFjZWM3NGIxZWZi MTcwOGQ3MWE5NGYwNWQlN0MwZmVlOGZmMmEzYjI0MDE4OWM3NTNhMWQ1NTkxZmVkYyU3QzElN0Mw JTdDNjM3MDA3MDk5MzEzMzA5MTUxJmFtcDtzZGF0YT1nJTJCcWcwRWRYV2lFdlFjNWlTZmo5anox Z3NUQ1NZcU0lMkZPdXdETTdJNHMzayUzRCZhbXA7cmVzZXJ2ZWQ9MA0K From nobody Tue Aug 6 15:42:18 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AAED12006E; Tue, 6 Aug 2019 15:42:16 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Linda Dunbar via Datatracker To: Cc: draft-ietf-curdle-ssh-ed25519-ed448.all@ietf.org, curdle@ietf.org, ietf@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Linda Dunbar Message-ID: <156513133597.27352.13434997644194654327@ietfa.amsl.com> Date: Tue, 06 Aug 2019 15:42:16 -0700 Archived-At: Subject: [Curdle] Genart telechat review of draft-ietf-curdle-ssh-ed25519-ed448-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Aug 2019 22:42:16 -0000 Reviewer: Linda Dunbar Review result: Ready I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please wait for direction from your document shepherd or AD before posting a new version of the draft. For more information, please see the FAQ at . Document: draft-ietf-curdle-ssh-ed25519-ed448-?? Reviewer: Linda Dunbar Review Date: 2019-08-06 IETF LC End Date: None IESG Telechat date: 2019-08-08 Summary: Major issues: Minor issues: Nits/editorial comments: The document has a few sentences to explain "public key algorithm for use with SSH in accordance with RFC4253, RFC4251" and give a name. and One sentence to say "Signatures are generated according to the procedure in RFC8032". I personally don't think it is a Standard Track document. Informational would be more appropriate. But there is no harm to be standard track. Linda Dunbar From nobody Tue Aug 6 20:21:18 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 16D9D1200D8; Tue, 6 Aug 2019 20:21:16 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: Suresh Krishnan via Datatracker To: "The IESG" Cc: draft-ietf-curdle-ssh-ed25519-ed448@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migaultf@ericsson.com, curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Suresh Krishnan Message-ID: <156514807605.27336.5657049259873011480.idtracker@ietfa.amsl.com> Date: Tue, 06 Aug 2019 20:21:16 -0700 Archived-At: Subject: [Curdle] Suresh Krishnan's No Objection on draft-ietf-curdle-ssh-ed25519-ed448-09: (with COMMENT) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 03:21:16 -0000 Suresh Krishnan has entered the following ballot position for draft-ietf-curdle-ssh-ed25519-ed448-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- * Section 5 "Signatures are generated according to the procedure in [RFC8032], Section 5.2.6 [RFC8032]." Shouldn’t this also include Section 5.1.6 of [RFC8032] to generate the signature using Ed25519? From nobody Tue Aug 6 23:42:20 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC7E1200E3; Tue, 6 Aug 2019 23:42:18 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= To: "The IESG" Cc: draft-ietf-curdle-ssh-ed25519-ed448@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migaultf@ericsson.com, curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= Message-ID: <156516013826.27352.2587066867552160397.idtracker@ietfa.amsl.com> Date: Tue, 06 Aug 2019 23:42:18 -0700 Archived-At: Subject: [Curdle] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-curdle-ssh-ed25519-ed448-09=3A_=28with_COMMENT=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 06:42:18 -0000 Éric Vyncke has entered the following ballot position for draft-ietf-curdle-ssh-ed25519-ed448-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-ed25519-ed448/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for this short document. I have one COMMENT and a couple of NITs though (minor and trivial to fix) === COMMENT === --- Section 2.1 --- Please use RFC 8174 boilerplate. === NIT === The "Ed25519" is capitalized in section 1 and all uppercase in section 7. Section 8 would benefit for editorial review regarding the use of ':' and starting sentence with a capitalized word. From nobody Wed Aug 7 08:59:09 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD6612045C; Wed, 7 Aug 2019 08:58:59 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Cc: draft-ietf-curdle-gss-keyex-sha2@ietf.org, curdle@ietf.org, The IESG , Daniel Migault , curdle-chairs@ietf.org, daniel.migault@ericsson.com, kaduk@mit.edu, rfc-editor@rfc-editor.org Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Message-ID: <156519353957.8454.1747539196416914763.idtracker@ietfa.amsl.com> Date: Wed, 07 Aug 2019 08:58:59 -0700 Archived-At: Subject: [Curdle] Protocol Action: 'GSS-API Key Exchange with SHA2' to Proposed Standard (draft-ietf-curdle-gss-keyex-sha2-10.txt) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 15:59:00 -0000 The IESG has approved the following document: - 'GSS-API Key Exchange with SHA2' (draft-ietf-curdle-gss-keyex-sha2-10.txt) as Proposed Standard This document is the product of the CURves, Deprecating and a Little more Encryption Working Group. The IESG contact persons are Benjamin Kaduk and Roman Danyliw. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-gss-keyex-sha2/ Technical Summary This document specifies additions and amendments to SSH GSS-API Methods [RFC4462]. It defines a new key exchange method that uses SHA-2 for integrity and deprecates weak DH groups. The purpose of this specification is to modernize the cryptographic primitives used by GSS Key Exchanges. Working Group Summary No serious issues were raised with this document, but it received little feedback overall. Document Quality The only currently know implementation are patches for OpenSSH in Fedora: https://src.fedoraproject.org/rpms/openssh/blob/master/f/openssh-7.5p1-gssapi-kex-with-ec.patch Personnel Daniel Migault is the document shepherd. Benjamin Kaduk is the responsible Area Director. RFC Editor Note In Section 5.1, sixth paragraph, please remove "according to Section 4 of [RFC5656]" from the first sentence; that reference is incorrect and RFC 7546 is (correctly) cited three paragraphs earlier. From nobody Mon Aug 12 15:52:10 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63A18120C5C for ; Mon, 12 Aug 2019 15:52:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 7H9VNve1Fxaa for ; Mon, 12 Aug 2019 15:52:06 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C238121331 for ; Mon, 12 Aug 2019 15:28:01 -0700 (PDT) Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x7CMRtmo013478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 12 Aug 2019 18:27:58 -0400 Date: Mon, 12 Aug 2019 17:27:55 -0500 From: Benjamin Kaduk To: Ron Frederick Cc: Mark Baushke , curdle Message-ID: <20190812222754.GE88236@kduck.mit.edu> References: <20190730214702.GS47715@kduck.mit.edu> <31257.1564525402@contrail-ubm16-mdb.svec1.juniper.net> <20190730231321.GU47715@kduck.mit.edu> <0D4BB5A9-5E34-4038-BD5B-1EE63A67447D@juniper.net> <7859169F-D86B-4027-B060-6BAA6FD6CA6A@timeheart.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7859169F-D86B-4027-B060-6BAA6FD6CA6A@timeheart.net> User-Agent: Mutt/1.10.1 (2018-07-13) Archived-At: Subject: Re: [Curdle] Second AD Review: draft-ietf-curdle-ssh-curves. X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Aug 2019 22:52:09 -0000 On Sun, Aug 04, 2019 at 09:51:51AM -0700, Ron Frederick wrote: > Hi Mark, > > On Aug 3, 2019, at 2:52 PM, Mark Baushke wrote: > > I have updated and uploaded the draft. Please let me know of any issues. > > > Here are a few thoughts on version 9 of the draft: > > In section 3, you say “Key-agreement schemes Curve25519 and Curve448”, but these algorithms are not key-agreement schemes by themselves. I’d recommend going with the proposed SSH names here if you are discussing the full key agreement scheme and not the underlying elliptic curve algorithms. In other words, I’d suggest “Key-agreement schemes curve25519-sha256 and curve448-sha512” (possibly with quotes around each), as done earlier in this section. That seems like a good suggestion, thanks. > When detecting the all-zeroes value, the new text says it should “abort if so, as described in Section 6” of RFC 7748. However, the original RFC doesn’t actually define what “abort” means. It says “abort if so (see below)”, but I don’t know what that is referring to. The only mention of “abort” is in sections 6.1 and 6.2, and nothing in section 7 seems to really expand on what should be done if the all-zeroes check matches. This is more a fault of RFC 7748 than it is of this doc, but since you are now recommending to “abort” in this doc, it would be good to be more specific about what that means for an SSH client/server. My read of 7748 is that the "(see below)" refers to the following paragraph, and is intended to expound on the all-zero check, not the act of aborting. Note that the second usage of "abort" does not have a "see below" note, which leads one to suspect that the referenced content is between the two mentions. It's probably okay for 7748 to be fairly generic about what "abort" means, since it's just defining the curves and not a protocol using them; for our usage in ssh it may suffice to make a brief reference to normal SSH error handling procedures. > I’m also not sure the sentence about “Alternative implementations” of these functions. There isn’t a lot of clarity on how one would determine in an alternate implementation when “either input forces the shared secret to one of a small set of values”. Since this point is covered already in RFC 7748 and this doc says “No further validation is required beyond what is discusses in RFC 7748”, though, I think it might be better to just leave this out. This is a recurring point of mild contention, whether to insist on a specific algorithm for performing group operations or just describing the group operations needed and the security considerations of using implementation algorithms other than the one specified. The mathematician in me is fine with specifying the curves using just the abstract mathematical description and noting that small-subgroup attacks exist, but I recognize that there are protocol-design considerations in nailing the procedure down tightly (at the cost of reducing implementation flexibility). While I'm pretty sure we have precedent in the IETF for both general approaches, I'm inclined to accept the "proven language from tcpcrypt" for now; there's always a chance the IETF LC and/or IESG will want to chime in, too. Given all that, I think it's okay to start the IETF LC, and we can wrap any changes in response to these comments up along with any other IETF LC comments. -Ben From nobody Mon Aug 12 16:33:15 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 43B3812000E; Mon, 12 Aug 2019 16:33:13 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Sender: CC: curdle@ietf.org, draft-ietf-curdle-ssh-curves@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migault@ericsson.com, kaduk@mit.edu Content-Transfer-Encoding: 7bit Reply-To: ietf@ietf.org Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Message-ID: <156565279324.20435.13150932630521903269.idtracker@ietfa.amsl.com> Date: Mon, 12 Aug 2019 16:33:13 -0700 Archived-At: Subject: [Curdle] Last Call: (Secure Shell (SSH) Key Exchange Method using Curve25519 and Curve448) to Proposed Standard X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Aug 2019 23:33:13 -0000 The IESG has received a request from the CURves, Deprecating and a Little more Encryption WG (curdle) to consider the following document: - 'Secure Shell (SSH) Key Exchange Method using Curve25519 and Curve448' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2019-08-26. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document describes the conventions for using Curve25519 and Curve448 key exchange methods in the Secure Shell (SSH) protocol. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Mon Aug 12 22:05:38 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54550120073 for ; Mon, 12 Aug 2019 22:05:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net 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 zF_Zv6XfRPS0 for ; Mon, 12 Aug 2019 22:05:35 -0700 (PDT) Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1636212007C for ; Mon, 12 Aug 2019 22:05:35 -0700 (PDT) Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x7D54qfC029370; Mon, 12 Aug 2019 22:05:31 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=to : cc : subject : in-reply-to : references : from : mime-version : content-type : content-id : date : message-id; s=PPS1017; bh=C9LvQCQkR+Ib9K+cnzLUmkAage3GMUx+D6hKjPxS7Gg=; b=IC4p0P+/iYIIRB76xPkmYQ5aF8BNZZdEzAIlzfGsv881gmlt3eQmDl2ZF++sGQ81cgWJ fGTU5ez6rcSZF/eoEo4Iq64qF5P+zgEPjEpwZFnRoswozn93y9EeX3psbqFEXTmyXr0d 0CUhg5o0xKhrHokySqeGGFJQYXULXXxcqZmToYgEPDQfZf+GC8svgae9rMONHQ4gBwHQ hdGQuJGXvZ9Dd6a0Nb7U2de76mZnc0757Vj3KTfoPmF+y4fG3mp68Ut9qZzL6c2HVqRZ W8s3hw8FJ0qFxC+3O+VTVQQhV3GyvI5bQpN0vpCXDVq/Sh8qRhKZvRdONN0Wxj+e2Bqc jQ== Received: from nam04-co1-obe.outbound.protection.outlook.com (mail-co1nam04lp2056.outbound.protection.outlook.com [104.47.45.56]) by mx0b-00273201.pphosted.com with ESMTP id 2ubkqh06r3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 12 Aug 2019 22:05:31 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YTNM6ocmwLvURmJZ2Ba0DVDSPeJ/HAD5vGBtr+7y6MDLitywz9pogsvIdop/nbLUNXu1xfMqjGim2PIZlXTQmVr52ivX/diHy2jXhfLyYJ6gCC/T+KRoR/gyaH8cPaxcsR6iJ2G3gMnF+JqQzeHBQx3ikk7dYYkpgiwouhr4dCgCd8Zi8x8+cvSoeOC4jTXpLYzZ/pCvL+84yznkk3QzbcIbhO/WBbpnOp//+DhBMvrumyg1V8Qrs5WRqdm344xreKNIEwYnKF48nXV6y1kz9rEjgHtlH3Z3D3hMPOSpQ9OtDdGxttfIswoK4XQxZu2IHpOkx7MsadIiYcMWR3EfQQ== 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=C9LvQCQkR+Ib9K+cnzLUmkAage3GMUx+D6hKjPxS7Gg=; b=lqNrw3sEOtgQ62OoSZzKyih7/oPyLkqh+Btpa+NB+b6LcixBWsGmcipl4/m5JatpyzZW60fGfgKNqftTHyPcf+QEU/iMpVL6X8nzO3HAYHHGyI0LobeqPrY4ZqJv/mWIRpAfvLRDVmH2fqLEREexSpxHQndNs/HTxNj1gFJq4qIksJywnWt2hWypElv9aRApbhXb7Wqjg2f6HB8LydZIqOqdD5Hdj6MHhsYcs6XPakWojBWOiEr56cwcqjxa58dcdAu8EE4P0N6wnl0BRZV9Tn4Srn17/9VmyJWggSR4WpDYjy++wFgwQjQ0lR4S8EP3JzlrRPKMTlGt+5AjstMksQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=softfail (sender ip is 66.129.239.12) smtp.rcpttodomain=ietf.org smtp.mailfrom=juniper.net; dmarc=fail (p=reject sp=reject pct=100) action=oreject header.from=juniper.net; dkim=none (message not signed); arc=none Received: from CH2PR05CA0001.namprd05.prod.outlook.com (2603:10b6:610::14) by BL0PR05MB4692.namprd05.prod.outlook.com (2603:10b6:208:29::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.8; Tue, 13 Aug 2019 05:05:26 +0000 Received: from CO1NAM05FT019.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::202) by CH2PR05CA0001.outlook.office365.com (2603:10b6:610::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2157.14 via Frontend Transport; Tue, 13 Aug 2019 05:05:26 +0000 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender) Received: from P-EXFEND-EQX-01.jnpr.net (66.129.239.12) by CO1NAM05FT019.mail.protection.outlook.com (10.152.96.127) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2178.6 via Frontend Transport; Tue, 13 Aug 2019 05:05:26 +0000 Received: from P-EXBEND-EQX-01.jnpr.net (10.104.8.52) by P-EXFEND-EQX-01.jnpr.net (10.104.8.54) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 12 Aug 2019 22:05:24 -0700 Received: from P-EXBEND-EQX-01.jnpr.net (10.104.8.52) by P-EXBEND-EQX-01.jnpr.net (10.104.8.52) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 12 Aug 2019 22:05:24 -0700 Received: from p-mailhub01.juniper.net (10.104.20.6) by P-EXBEND-EQX-01.jnpr.net (10.104.8.52) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Mon, 12 Aug 2019 22:05:24 -0700 Received: from contrail-ubm16-mdb.svec1.juniper.net ([10.163.18.199]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id x7D55NIg015087; Mon, 12 Aug 2019 22:05:23 -0700 (envelope-from mdb@juniper.net) To: Benjamin Kaduk CC: Ron Frederick , curdle In-Reply-To: <20190812222754.GE88236@kduck.mit.edu> References: <20190730214702.GS47715@kduck.mit.edu> <31257.1564525402@contrail-ubm16-mdb.svec1.juniper.net> <20190730231321.GU47715@kduck.mit.edu> <0D4BB5A9-5E34-4038-BD5B-1EE63A67447D@juniper.net> <7859169F-D86B-4027-B060-6BAA6FD6CA6A@timeheart.net> <20190812222754.GE88236@kduck.mit.edu> Comments: In-reply-to: Benjamin Kaduk message dated "Mon, 12 Aug 2019 17:27:55 -0500." From: "Mark D. Baushke" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <783.1565672722.1@contrail-ubm16-mdb.svec1.juniper.net> Date: Mon, 12 Aug 2019 22:05:23 -0700 Message-ID: <784.1565672723@contrail-ubm16-mdb.svec1.juniper.net> X-EXCLAIMER-MD-CONFIG: e3cb0ff2-54e7-4646-8a04-0dae4ac7b136 X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-HT: Tenant X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(4636009)(39860400002)(376002)(136003)(346002)(396003)(2980300002)(199004)(189003)(11346002)(486006)(5660300002)(126002)(476003)(14444005)(8936002)(23726003)(2906002)(46406003)(305945005)(356004)(8676002)(81166006)(81156014)(97876018)(50466002)(117636001)(76176011)(7696005)(16586007)(316002)(26005)(54906003)(446003)(478600001)(4326008)(47776003)(6916009)(97756001)(2171002)(336012)(53936002)(70206006)(229853002)(70586007)(6246003)(86362001)(426003)(186003); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR05MB4692; H:P-EXFEND-EQX-01.jnpr.net; FPR:; SPF:SoftFail; LANG:en; PTR:InfoDomainNonexistent; A:1; MX:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: e188b903-f475-45fd-dde8-08d71fabda84 X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(4710121)(4711136)(1401327)(2017052603328); SRVR:BL0PR05MB4692; X-MS-TrafficTypeDiagnostic: BL0PR05MB4692: X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:10000; X-Forefront-PRVS: 01283822F8 X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: cJtUn8WmVSFdMA0Oq2sWD1CTiEuB+Ml5jnE4AhelXefN/HjVURDWMTOnC+i8QngyhCtUIAINbrRP4P76xfs4cu54+MRqMdcVDschRpsWqzAQB89u5xLsBEJXoCifNM1c5w7tIxZ3xK5ojq07tCtauCIccUAnSmLI6GXPT2lqcEuUFC94mFhGxP2+bH70zM0aj/JUA4++JhRPhLkwBpIlfHvElNdhkpAcr5UwyXwHZfoCo147maa243rpoG+Ud2dh62Yg/v8KU10lZxAp1tixDoDKhTdJbL/2zwPCWFjpoTBfCqY/pBCfKsj06YygH5XX5CuTxxNTQNfDM7HL9YnS4NnF/IKkQbgPil51vw+7bE5M+5lfrzwh6i7uHP2q4bQRCYq3KVPeOIxCL9S10CgnyABIyXdHavnIpq9XNMYgUq4= X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Aug 2019 05:05:26.1136 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: e188b903-f475-45fd-dde8-08d71fabda84 X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12]; Helo=[P-EXFEND-EQX-01.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR05MB4692 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-13_01:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908130054 Archived-At: Subject: Re: [Curdle] Second AD Review: draft-ietf-curdle-ssh-curves. X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Aug 2019 05:05:36 -0000 Hi Ron & Ben, Modulo the date stamp changes and the line break changes, here is what the modified text looks like after trying to address the comments you both made. Let me know if I captured your intended changes correctly or not. I can either upload a new version, or just roll these changes into the next version after addressing any other comments during LC. Thanks, -- Mark --- draft-ietf-curdle-ssh-curves-09.txt 2019-08-03 14:44:28.000000000 -0700 +++ draft-ietf-curdle-ssh-curves-10.txt 2019-08-12 21:55:24.000000000 -0700 @@ -133,21 +133,25 @@ are generated as described therein. Public keys are defined as strings of 32 bytes for Curve25519 and 56 bytes for Curve448. - Key-agreement schemes Curve25519 and Curve448 perform the Diffie- - Helman protocol using the functions X25519 and X448, respectively. - Implementations SHOULD compute these functions using the algorithms - described in [RFC7748]. When they do so, implementations MUST check - whether the computed Diffie-Hellman shared secret is the all-zero - value and abort if so, as described in Section 6 of [RFC7748]. - Alternative implementations of these functions SHOULD abort when - either input forces the shared secret to one of a small set of - values, as discussed in Section 7 of [RFC7748]. Clients and servers - MUST fail the key exchange if the length of the received public keys - are not the expected lengths. No further validation is required - beyond what is discussed in [RFC7748]. The derived shared secret is - 32 bytes when Curve25519 is used and 56 bytes when Curve448 is used. - The encodings of all values are defined in [RFC7748]. The hash used - is SHA-256 for Curve25519 and SHA-512 for Curve448. + Key-agreement schemes "curve25519-sha256" and "curve448-sha512" + perform the Diffie-Helman protocol using the functions X25519 and + X448, respectively. Implementations SHOULD compute these functions + using the algorithms described in [RFC7748]. When they do so, + implementations MUST check whether the computed Diffie-Hellman shared + secret is the all-zero value and abort if so, as described in + Section 6 of [RFC7748]. Alternative implementations of these + functions SHOULD abort when either input forces the shared secret to + one of a small set of values, as discussed in Section 7 of [RFC7748]. + Clients and servers MUST fail the key exchange if the length of the + received public keys are not the expected lengths. An abort for + these purposes is defined as a disconnect of the session with an + appropriate SSH "protocol error" for the fault provided to or by the + client. No further validation is required beyond what is discussed + in [RFC7748]. The derived shared secret is 32 bytes when + "curve25519-sha256" is used and 56 bytes when "curve448-sha512" is + used. The encodings of all values are defined in [RFC7748]. The + hash used is SHA-256 for "curve25519-sha256" and SHA-512 for + "curve448-sha512". 3.1. Shared Secret Encoding @@ -158,9 +162,9 @@ The shared secret, K, is defined in [RFC4253] and [RFC5656] as an integer encoded as a multiple precision integer (mpint). - Curve25519/448 outputs a binary string X, which is the 32 or 56 byte - point obtained by scalar multiplication of the other side's public - key and the local private key scalar. The 32 or 56 bytes of X are + Curve25519/448 outputs a binary string X, which is the 32 or 56 byte + point obtained by scalar multiplication of the other side's public + key and the local private key scalar. The 32 or 56 bytes of X are converted into K by interpreting the octets as an unsigned fixed- length integer encoded in network byte order. @@ -215,8 +218,8 @@ The way the derived binary secret string is encoded into a mpint before it is hashed (i.e., adding or removing zero-bytes for encoding) raises the potential for a side-channel attack which could - determine the length of what is hashed. This would leak the most - significant bit of the derived secret, and/or allow detection of when + determine the length of what is hashed. This would leak the most + significant bit of the derived secret, and/or allow detection of when the most significant bytes are zero. For backwards compatibility reasons it was decided not to address this potential problem. From nobody Wed Aug 14 20:58:59 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E0E120018 for ; Wed, 14 Aug 2019 20:58:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 GX4wCnQufx0N for ; Wed, 14 Aug 2019 20:58:56 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFAD612002E for ; Wed, 14 Aug 2019 20:58:55 -0700 (PDT) Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x7F3woeT025060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 14 Aug 2019 23:58:52 -0400 Date: Wed, 14 Aug 2019 22:58:49 -0500 From: Benjamin Kaduk To: "Mark D. Baushke" Cc: Ron Frederick , curdle Message-ID: <20190815035849.GK88236@kduck.mit.edu> References: <20190730214702.GS47715@kduck.mit.edu> <31257.1564525402@contrail-ubm16-mdb.svec1.juniper.net> <20190730231321.GU47715@kduck.mit.edu> <0D4BB5A9-5E34-4038-BD5B-1EE63A67447D@juniper.net> <7859169F-D86B-4027-B060-6BAA6FD6CA6A@timeheart.net> <20190812222754.GE88236@kduck.mit.edu> <784.1565672723@contrail-ubm16-mdb.svec1.juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <784.1565672723@contrail-ubm16-mdb.svec1.juniper.net> User-Agent: Mutt/1.10.1 (2018-07-13) Archived-At: Subject: Re: [Curdle] Second AD Review: draft-ietf-curdle-ssh-curves. X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Aug 2019 03:58:57 -0000 On Mon, Aug 12, 2019 at 10:05:23PM -0700, Mark D. Baushke wrote: > Hi Ron & Ben, > > Modulo the date stamp changes and the line break changes, here is what > the modified text looks like after trying to address the comments you > both made. > > Let me know if I captured your intended changes correctly or not. Yes, that works for me. > I can either upload a new version, or just roll these changes into the > next version after addressing any other comments during LC. Either way is fine; personally, I would wait until more comments come in. Thanks! -Ben From nobody Thu Aug 22 05:00:41 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2E7120820; Thu, 22 Aug 2019 05:00:38 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: Christer Holmberg via Datatracker To: Cc: curdle@ietf.org, ietf@ietf.org, draft-ietf-curdle-ssh-curves.all@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Christer Holmberg Message-ID: <156647523885.14827.16394888562228822662@ietfa.amsl.com> Date: Thu, 22 Aug 2019 05:00:38 -0700 Archived-At: Subject: [Curdle] Genart last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Aug 2019 12:00:39 -0000 Reviewer: Christer Holmberg Review result: Ready with Nits I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at . Document: draft-ietf-curdle-ssh-curves-09 Reviewer: Christer Holmberg Review Date: 2019-08-22 IETF LC End Date: 2019-08-26 IESG Telechat date: Not scheduled for a telechat Summary: The document is almost ready for publication. I have no technical issues, but there are some issues in Section 1 that I'd like to authors to address. Major issues: N/A Minor issues: N/A Nits/editorial comments: General: --------- QGEN_1: - The document uses “as discussed in”, “as defined in”, “as described” in terminology. It might be justified to use different terminology in some cases, but in general I suggest trying to use consistent terminology. Section 1: ---------- Q1_1: The text says: ”[RFC5656] describes how elliptic curves are integrated in SSH, and this document reuses those protocol messages.” …and: “This document describes how to implement key exchange based on Curve25519 and Curve448 [RFC7748] in SSH.” - It is unclear to me what “integrated in SSH” means. Does it mean that RFC 5656 describes the generic procedures for performing SSH key exchanges using elliptic curves, or does it also cover other things? - I think the “this document reuses those protocol messages” sounds a little confusing because I don’t know what “those protocol message” refers to. Perhaps say something like “reuses the protocol messages defined in that specification”. Q1_2: - I don’t think you should use “we” terminology (“we describe”, “we chose”, etc..). Please talk about the document, and if you want to refer to a choice made by the WG please indicate that. Q1_3: - Instead of “currently”, I suggest to say something like “at the time of publication”. Because, the meaning of “currently” changes every second :) Q1_4: The text says: “The Curve448 key exchange method is novel but similar in spirit,” - I don’t know what this means, since there is now further explanation. Q1_5: The text says: “This document provide Curve25519 as the preferred choice, but suggests that the fall back option Curve448 is implemented to provide an hedge against unforeseen analytical advances against Curve25519 and SHA-256.” - Is the only reason why one should implement Curve448 that something MAY happen to Curve25519 in the future? - Also, is there anything preventing unforeseen analytical advances against Curve448? From nobody Sun Aug 25 04:21:37 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 553AE1200E3; Sun, 25 Aug 2019 04:21:23 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Tobias Gondrom via Datatracker To: Cc: curdle@ietf.org, ietf@ietf.org, draft-ietf-curdle-ssh-curves.all@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Tobias Gondrom Message-ID: <156673208322.31181.16685593489316726586@ietfa.amsl.com> Date: Sun, 25 Aug 2019 04:21:23 -0700 Archived-At: Subject: [Curdle] Secdir last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 11:21:23 -0000 Reviewer: Tobias Gondrom Review result: Ready I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. The summary of the review is Ready. This document describes how to implement key exchange based on Elliptic Curve Curve25519 (with SHA256) and Curve448 (with SHA512) in SSH. Note: the curve25519-sha256 key exchange is similar to the "curve25519-sha256@libssh.org" key exchange method implemented in libssh and OpenSSH. One thought: I am not cryptographer enough to give a proper recommendation as to the suitability of Curve448 with SHA-512. The reviews state that they would be similar, but with Curve448 not having received the same amount of cryptographic review. I am a bit cautious on assuming it would be good fallback in case Curve25519 would be considered weakened by cryptographic advances. Surely extending the hash to 512 can be helpful, but as both Curve448 and Curve25519 seem to rely on similar principles, the advances that might weaken 25519 might sooner or later also impact 448. Considering that 448 has not had so many reviews, I am not sure whether it is helpful to add it as a fallback. In case of new advances, 448 would have to be reviewed more closely before a general fallback would be recommended. This is only my personal view with limited background in cryptography. However, equally, it might be prudent to add 448 in this document now as it is and then schedule the deeper review once new breakthroughs are being discovered that weaken 25519. One minor spelling nits: section 5: ...but it is provided as an hedge/ but it is provided as a hedge Overall the draft is ready to go. Best regards, Tobias From nobody Sun Aug 25 16:52:06 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DB2F51200C4; Sun, 25 Aug 2019 16:52:04 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: rsalz@akamai.com, curdle@ietf.org, curdle-chairs@ietf.org, kaduk@mit.edu X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <156677712484.31069.11160834903274335687.idtracker@ietfa.amsl.com> Date: Sun, 25 Aug 2019 16:52:04 -0700 Archived-At: Subject: [Curdle] curdle - Not having a session at IETF 106 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 23:52:05 -0000 Rich Salz, a chair of the curdle working group, indicated that the curdle working group does not plan to hold a session at IETF 106. This message was generated and sent by the IETF Meeting Session Request Tool. From nobody Mon Aug 26 09:29:14 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F36601200DF; Mon, 26 Aug 2019 09:28:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net 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 X_PUrncQ2WjD; Mon, 26 Aug 2019 09:28:55 -0700 (PDT) Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6066120072; Mon, 26 Aug 2019 09:28:54 -0700 (PDT) Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x7QGONFF028813; Mon, 26 Aug 2019 09:28:47 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=to : cc : subject : in-reply-to : references : from : mime-version : content-type : content-transfer-encoding : date : message-id; s=PPS1017; bh=Mn5qYR7o09KULipCg0c+n6cn1UKaqZ4LOwf1bDX2of0=; b=MI4jvZKQEYriuvSIelyMcz1kMxRliRD86TihxRNaeBJcvZR9ZSopuAR6Ygysxys+lf2h tlQxY2BS3wmFzSQyNvcECo72l1zd0Dpjg2+7QzINUXdwtww3zIlj42zkv/q5fOhllTDQ 5gy0vTzPWjGS0Yy6pkznBhsk2R6/8PGjG7fDgjVBF6m9rwp3i7yr0/YphZ/cSDuZnymZ cvbodVUVDs+M33evYAu1j43ov9EkrVdrz50cKTcZcSf8evbwcOej7t0ON+vjQv2tMQc7 oAM/3SIImEFShUcRS4/eQqImmXXWfMAG7OAY7tmlwJfW6FAwEs0rX3CKxMsvEOpFWwzr 1Q== Received: from nam01-by2-obe.outbound.protection.outlook.com (mail-by2nam01lp2053.outbound.protection.outlook.com [104.47.34.53]) by mx0a-00273201.pphosted.com with ESMTP id 2uknf6t0fc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 26 Aug 2019 09:28:46 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=b7aFetXTYJRRnXRFgw8Zr+4FKoH+jp08+Ub8DYV6Zcf6iPX4zGctp6iw3hF6sF8RL/cArO5HHLCUUXCr4X4qYqkRPmz6i883JH5zIAY3kK4GNNDVzY86N64q0IIPClW8VAQh7BTkKcLd5AyoZVsQZC2eqn3aImNEiVINv+rv7oS2dWSEY0XGLnMZcX4FMzoNgTewl3B4bMonj3OEBCwV4ypYpr8K4wR2Uhai31WYiQnYy3U8Pb7nx/N9EP8ABrsyfcxoigVthgvMmJZJuNBZsVSjfcjTph+Zk1uS/oIwrbjtO0JCXK+LjW+S80SEAOquDkDEO4WjeDty3Q6cFpkcvA== 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=Mn5qYR7o09KULipCg0c+n6cn1UKaqZ4LOwf1bDX2of0=; b=YON8GR03Ih8OPU7aVrYGfNXXvFWBn0X/iQ0N6qLz66bX1jHBebsi+Rvzh92pqQJR9t/LGVVX+o0C7RqJMP5vhjxU7ebcpqTX/2Da90S+LNknk/LPQkUg12gjQZCb+czd98yDUkaNYAYiYCis9Jz65piAArdngk2B1rJ/1aD8NP5MI54bFVxJfR9GZNc1DNLptHdbfMa9I876WyE8rLLswJ1qpU3dlRRa2yvkd3moKgOLvGcxpvJbpmeAoaEKI84YsCr0nuGSGyYwuQ2opj1YtNjQT3TjGfJYnHkinxPOR/+evYWMV2X7BEjE4YdSjKaBiW0IUjzMs0GHu4A3wrHBJw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=softfail (sender ip is 66.129.239.12) smtp.rcpttodomain=ietf.org smtp.mailfrom=juniper.net; dmarc=fail (p=reject sp=reject pct=100) action=oreject header.from=juniper.net; dkim=none (message not signed); arc=none Received: from SN4PR0501CA0078.namprd05.prod.outlook.com (2603:10b6:803:22::16) by BN3PR05MB2706.namprd05.prod.outlook.com (2a01:111:e400:7bb4::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.13; Mon, 26 Aug 2019 16:28:45 +0000 Received: from BY2NAM05FT005.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::208) by SN4PR0501CA0078.outlook.office365.com (2603:10b6:803:22::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.7 via Frontend Transport; Mon, 26 Aug 2019 16:28:45 +0000 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender) Received: from P-EXFEND-EQX-01.jnpr.net (66.129.239.12) by BY2NAM05FT005.mail.protection.outlook.com (10.152.100.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2220.7 via Frontend Transport; Mon, 26 Aug 2019 16:28:44 +0000 Received: from P-EXBEND-EQX-01.jnpr.net (10.104.8.52) by P-EXFEND-EQX-01.jnpr.net (10.104.8.54) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 26 Aug 2019 09:28:44 -0700 Received: from P-EXBEND-EQX-01.jnpr.net (10.104.8.52) by P-EXBEND-EQX-01.jnpr.net (10.104.8.52) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 26 Aug 2019 09:28:43 -0700 Received: from p-mailhub01.juniper.net (10.104.20.6) by P-EXBEND-EQX-01.jnpr.net (10.104.8.52) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Mon, 26 Aug 2019 09:28:43 -0700 Received: from contrail-ubm16-mdb.svec1.juniper.net ([10.163.18.199]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id x7QGSgqT028384; Mon, 26 Aug 2019 09:28:42 -0700 (envelope-from mdb@juniper.net) To: Christer Holmberg CC: , , , In-Reply-To: <156647523885.14827.16394888562228822662@ietfa.amsl.com> References: <156647523885.14827.16394888562228822662@ietfa.amsl.com> Comments: In-reply-to: Christer Holmberg via Datatracker message dated "Thu, 22 Aug 2019 05:00:38 -0700." From: "Mark D. Baushke" X-Phone: +1 408 745-2952 (Office) X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1 X-Face: #8D_6URD2G%vC.hzU X-EXCLAIMER-MD-CONFIG: e3cb0ff2-54e7-4646-8a04-0dae4ac7b136 X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-HT: Tenant X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(4636009)(136003)(376002)(346002)(39860400002)(396003)(2980300002)(189003)(199004)(97876018)(4326008)(6916009)(305945005)(126002)(966005)(5660300002)(11346002)(446003)(2486003)(7696005)(23676004)(76176011)(117636001)(336012)(8936002)(6306002)(47776003)(50226002)(53936002)(6246003)(81166006)(316002)(478600001)(54906003)(14444005)(476003)(70586007)(70206006)(2906002)(229853002)(356004)(486006)(186003)(86362001)(50466002)(26005)(8676002)(81156014)(426003)(8746002)(62816006); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR05MB2706; H:P-EXFEND-EQX-01.jnpr.net; FPR:; SPF:SoftFail; LANG:en; PTR:InfoDomainNonexistent; MX:1; A:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 4baaac91-dca0-49d1-99fe-08d72a4276d0 X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(4710121)(4711137)(1401327)(4618075)(2017052603328); SRVR:BN3PR05MB2706; X-MS-TrafficTypeDiagnostic: BN3PR05MB2706: X-MS-Exchange-PUrlCount: 1 X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:10000; X-Forefront-PRVS: 01415BB535 X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: aOVISmlSZBLOxTAAVNz7r1oYmwcUAn/kUyWijQoNp9Xa4VSr0AnuIttuaxpJQiKSpBEKyKGnwf8xhYqJ94TVFH0eiDh/MQxaZ88NsCB0DgF42KAczqori5fVQDQBltEe8JwNur4aXP7Sgl8sllw6pH4WkbemicfQYAYDREntFnV55T2USpqpgt1d5xwngz/gpec9F7dY4l05E/xjHELC2YX1QEwPlW/bpf+3ovfi53pxV0GG4MBXhUdHup19HUGwWj7WOYKLmZh/6oUOfePIpkT66EJluLEQmxrAalXZ1ePTlojAVCZJYgGy7lPt5LjaYpvcA8NMJV2tSXQGEZOrbVlHHesTyr42Alz95DOViKr3V+wYCvg6wI3y60kL4EvUrXz3aHR2jMTs6/zQMKY9mLyt6PeI6P3b2UaufOx45LA= X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Aug 2019 16:28:44.5304 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 4baaac91-dca0-49d1-99fe-08d72a4276d0 X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12]; Helo=[P-EXFEND-EQX-01.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2706 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-26_08:2019-08-26,2019-08-26 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 bulkscore=0 clxscore=1011 priorityscore=1501 malwarescore=0 phishscore=0 spamscore=0 impostorscore=0 lowpriorityscore=0 mlxscore=0 suspectscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908260162 Archived-At: Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 16:28:58 -0000 Hi Christer, Christer Holmberg via Datatracker writes: > Reviewer: Christer Holmberg > Review result: Ready with Nits > > I am the assigned Gen-ART reviewer for this draft. The General Area > Review Team (Gen-ART) reviews all IETF documents being processed > by the IESG for the IETF Chair. Please treat these comments just > like any other last call comments. Okay. > For more information, please see the FAQ at > > https://trac.ietf.org/trac/gen/wiki/GenArtfaq > > Document: draft-ietf-curdle-ssh-curves-09 > Reviewer: Christer Holmberg > Review Date: 2019-08-22 > IETF LC End Date: 2019-08-26 > IESG Telechat date: Not scheduled for a telechat > > Summary: > > The document is almost ready for publication. I have no technical issues,= but > there are some issues in Section 1 that I'd like to authors to address. > > Major issues: N/A > > Minor issues: N/A > > Nits/editorial comments: > > General: > --------- > > QGEN_1: > > - The document uses =E2=80=9Cas discussed in=E2=80=9D, =E2=80=9Cas define= d in=E2=80=9D, =E2=80=9Cas described=E2=80=9D > in terminology. It might be justified to use different terminology in > some cases, but in general I suggest trying to use consistent > terminology. I understand. Only occurance of "as discussed in" is found in this text: "Alternative implementations of these functions SHOULD abort when either input forces the shared secret to one of a small set of values, as discussed in Section 7 of [RFC7748]." Section 7 of RFC7748 is the Security Considerations section and is a discussion of the elements which are potentially a security issue during implementation. This draft provides a SHOULD recommendation to abort the connection when one of these raised security considerations is found. That said, I am okay with changing the text to "Alternative implementations of these functions SHOULD abort when either input forces the shared secret to one of a small set of values, as described in Section 7 of [RFC7748]." The only other time the word discussed is used is in No further validation is required beyond what is discussed in . which may be replaced with No further validation is required beyond what is described in . I was unable to find any "as defined in" statements. I found declarative statements "is defined in" "are defined in" "is defined as" which were references to normative protocol elements. The use of "as described in" is found in the standard boilerplate copyright notice and the boilerplate Requirements language sections. So, I have migrated from "discussed" to described" for consistentcy. > Section 1: > ---------- > > Q1_1: > > The text says: > > =E2=80=9D[RFC5656] describes how elliptic curves are > integrated in SSH, and this document reuses those protocol messages.= =E2=80=9D > > =E2=80=A6and: > > =E2=80=9CThis document describes how to implement key exchange based on > Curve25519 and Curve448 [RFC7748] in SSH.=E2=80=9D > > - It is unclear to me what =E2=80=9Cintegrated in SSH=E2=80=9D mean= s. The title of RFC 5656 is "Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer" and this Draft intents to augment the Elliptic Curve methods defined there. > Does it mean that RFC 5656 describes the generic procedures for > performing SSH key exchanges using elliptic curves, or does it also > cover other things? RFC5656 covers three specific constructions: a) Elliptic Curve Diffie-Hellman (ECDH), b) Elliptic Curve Menezes-Qu-Vanstone (ECMQV) key agreement, and c) Elliptic Curve Digital Signature Algorithm (ECDSA). This draft does not cover the use of a digital signature algoirthm or apply the Curve25519 or Curve448 constructions to the use of ECMQV and focuses entirely on ECDH key exchange extensions for a different construction of elliptic curves. > - I think the =E2=80=9Cthis document reuses those protocol messages=E2=80= =9D sounds a > little confusing because I don't know what =E2=80=9Cthose protocol messag= e=E2=80=9D > refers to. Perhaps say something like =E2=80=9Creuses the protocol messag= es > defined in that specification=E2=80=9D. This draft resuses the SSH_MSG_KEX_ECDH_INIT and SSH_MSG_KEX_ECDH_REPLY messages which apply to the ECDH construction as in in section 4 of this draft. Does this paragraph work as a better replacement for the first paragraph of the introduction? Or, is it too detailed for a summary introduction? Secure Shell (SSH) is a secure remote login protocol. The key exchange protocol described in supports an extensible set of methods. defines how elliptic curves are integrated into this extensible SSH framework, and this document reuses the Elliptic Curve Diffie-Hellman (ECDH) key exchange protocol messages defined in section 7.1 "ECDH Message Numbers" . It seems a bit detailed to me for an introduction. Let me know if you have any suggestions on a revision. > Q1_2: > > - I don't think you should use =E2=80=9Cwe=E2=80=9D terminology (=E2=80= =9Cwe describe=E2=80=9D, =E2=80=9Cwe chose=E2=80=9D, > etc..). Please talk about the document, and if you want to refer to a cho= ice > made by the WG please indicate that. Fixed. > Q1_3: > > - Instead of =E2=80=9Ccurrently=E2=80=9D, I suggest to say something like= =E2=80=9Cat the time of > publication=E2=80=9D. Because, the meaning of =E2=80=9Ccurrently=E2=80=9D= changes every second :) Fixed. > Q1_4: > > The text says: > > =E2=80=9CThe Curve448 key exchange method is novel but similar in spirit,= =E2=80=9D > > - I don't know what this means, since there is now further explanation. The paragraph now reads: This document describes how to implement key exchange based on Curve25519 and Curve448 in SSH. For Curve25519 with SHA-256 , the algorithm described is equivalent to the privately defined algorithm "curve25519-sha256@libssh.org", which at the time of publication was implemented and widely deployed in libssh and OpenSSH. The Curve448 key exchange method is similar but uses SHA-512 to further separate it from the Curve25519 alternative. Would you rather that I use 'This document defines ...' here and in the abstract rather than 'This document describes ...' ? Please advise. > Q1_5: > > The text says: > > =E2=80=9CThis document provide Curve25519 as the preferred choice, but > suggests that the fall back option Curve448 is implemented to provide > an hedge against unforeseen analytical advances against Curve25519 > and SHA-256.=E2=80=9D > > - Is the only reason why one should implement Curve448 that something > MAY happen to Curve25519 in the future? No, the Curve448 also has a stronger cryptographic security strength. If it becomes a requirement to use a minimum of 128 bits of security strength, then Curve25519 may be rejected by some and thus the need to provide for something stronger. > - Also, is there anything preventing unforeseen analytical advances > against Curve448? There is nothing preventing any unforeseen analytical advances against any of the current public key implementations. This is why Post-Quantum-Cryptographic (PQC) is such a host topic today. However, the same tools which may be able to exploit EcDSA may not be as quickly pointed at these curves. Cryptographic agility is the key here. Let me know if you which to have me remove the entire paragraph or not. This document provide Curve25519 as the preferred choice, but suggests that the fall back option Curve448 is implemented to provide an hedge against unforeseen analytical advances against Curve25519 and SHA-256. Due to different implementation status of these two curves (high-quality free implementations of Curve25519 has been in deployed use for several years, while Curve448 implementations are slowly appearing), it is accepted that adoption of Curve448 will be slower. Should I upload my updated draft-ietf-curdle-ssh-curves-10.xml or do you have additional suggestions? Thank you, -- Mark From nobody Mon Aug 26 10:37:28 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63FA0120B31; Mon, 26 Aug 2019 10:37:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.002 X-Spam-Level: X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com 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 buAlRZBGsB7x; Mon, 26 Aug 2019 10:37:22 -0700 (PDT) Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140059.outbound.protection.outlook.com [40.107.14.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EB65120AEB; Mon, 26 Aug 2019 10:37:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hvphiCJkLVAXRoMxUGOzVr65Zv0iHu+YhTTAL3mbw7s6/U2yAroAD4NQogJTY3OFdUBGY9gj1ZTyF/O4nkxUcSWtht1pGhn2cWjpOREee8Ypm9Mjt1iV0MWqkuPeYILS0CnNfam6q5M347HzeHmn/+6P/iqeOvuGvGiXAnh83XXriPSA51JyNob/ZuoYi0EDlCIZFRdG8S9ioOuAY4SWQg8mgFiZEfEy1ez3lM0uzyqHFjjUxxzhTlaa7KinwEVRDRT9B1bECqLwqB841Zdjvg3sYVhCWJIghO9o+e6nkYqcQSlC5/jnDna8/pGKFu5Bgsw8uvhAw/Yd9DzNPifiQg== 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=j9xxsWIeJjv5LMsY9BQfQ+MtzYWMwIYS2+pEEKpeWPU=; b=WGCBlRSfgrMunQ6UNPFg/hnjKhQpjpTBHMSr9Mqs/n8yTQIY3Dg0jbpiX2663eEaSQFPcW3DMpjWETPebDzKbWmkYEXcvOS94/K/VhaVfSS9MxY7nPT/dnq7lm2LOhfKgb3AkItr68LsvFULLjVXHXTMrAnM1Muf/Z1wtR2DimfHkw1nMC8/U+WUD5UrOkanV1W6rRDqroNJmNibJ/KQdLyvaHMSK5MBIbN/EQoeQFw2S3CDq2ZPYWaJtv5vMpu5n0O7yOd/1rUXxaWiq8aNHKsXXk3meFes/vTUQfB+Dno9NkaTt5qF3qMEnRY8Hb2X7phRKNSYTgDk3VgFRzPTWQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=j9xxsWIeJjv5LMsY9BQfQ+MtzYWMwIYS2+pEEKpeWPU=; b=F40Z7HceF5UCli1coVQ9C8jK5Cs+KIPHvUaa78kWlzimIbqclINHrCXWvGStPd2ZMNY/t0k0VWTnkZOfrsFPX+6AGCDAkL8Ys6GD22Kx93Ne/ADJRhWXrXWK2XpZPpgCXjJjhwrPqRfpCfX3N8LbF7PZalYsuZEAs2mv3SlQbOU= Received: from VI1PR07MB3167.eurprd07.prod.outlook.com (10.175.243.17) by VI1PR07MB5327.eurprd07.prod.outlook.com (20.178.11.209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.14; Mon, 26 Aug 2019 17:37:16 +0000 Received: from VI1PR07MB3167.eurprd07.prod.outlook.com ([fe80::d031:8cb6:bfb:dc3]) by VI1PR07MB3167.eurprd07.prod.outlook.com ([fe80::d031:8cb6:bfb:dc3%3]) with mapi id 15.20.2199.021; Mon, 26 Aug 2019 17:37:16 +0000 From: Christer Holmberg To: "Mark D. Baushke" CC: "gen-art@ietf.org" , "curdle@ietf.org" , "ietf@ietf.org" , "draft-ietf-curdle-ssh-curves.all@ietf.org" Thread-Topic: Genart last call review of draft-ietf-curdle-ssh-curves-09 Thread-Index: AQHVXCtcvr2YSg9UakaoGGnxJPuFPKcNqHWs Date: Mon, 26 Aug 2019 17:37:16 +0000 Message-ID: References: <156647523885.14827.16394888562228822662@ietfa.amsl.com>, <19556.1566836922@contrail-ubm16-mdb.svec1.juniper.net> In-Reply-To: <19556.1566836922@contrail-ubm16-mdb.svec1.juniper.net> 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=christer.holmberg@ericsson.com; x-originating-ip: [79.134.118.162] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 9ee58ba6-cf25-41d1-5614-08d72a4c0999 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:VI1PR07MB5327; x-ms-traffictypediagnostic: VI1PR07MB5327: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 01415BB535 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(396003)(136003)(376002)(346002)(366004)(189003)(199004)(54906003)(102836004)(66946007)(76116006)(6506007)(53936002)(3846002)(7696005)(316002)(6116002)(66476007)(66556008)(64756008)(66446008)(71190400001)(256004)(74316002)(14454004)(14444005)(26005)(66066001)(6436002)(55016002)(9686003)(1941001)(52536014)(8676002)(25786009)(4326008)(305945005)(5660300002)(186003)(86362001)(7736002)(71200400001)(76176011)(33656002)(2906002)(8936002)(6916009)(99286004)(486006)(476003)(478600001)(11346002)(81156014)(229853002)(446003)(6246003)(44832011)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB5327; H:VI1PR07MB3167.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: hrbJxMyEoz2U2k8Bobeejxpqtbq0xVP6X4W89GIp6P8SRUD7khM7eAt/wcvdVVkOMtDD4FRGPW/Jz74UT6l95LSNvbPIb8R/IQRkRtVGajdJbe8HlHHbzzKHJ361rMPu14MC1/7M1hUnbaiQHpd4b6V0L2EilaZ74OrRBZC24tkeiYlADBnYE0qKdt0lnYWhPMvaRmzgLTcgiI04ydeRnAfitsNqAAN9raJcrFZbCi3ygrvH5S5brjcTfQ4hdGc5gt6DnSCA8XCZXj1ODi6z3G84WnY4LXyZS7ympnvxjKo8RX/hiuiWeyL/y8/HDEagXiE9y8GDRLdWP4ZWS8JYlLoMylI0sdzQcNyq9hzDRrCbH3TZNk6FcgeKzyLzleiMrG30z0WZRB6QPAHmVZwOcSPK1cFzdBQDeE38u73f8Z0= x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-Network-Message-Id: 9ee58ba6-cf25-41d1-5614-08d72a4c0999 X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Aug 2019 17:37:16.2589 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: pOWHW7qyXe0mGyjflgByXW4HeLddHq+fqWbpGUUs9SuRPFwbDZprtnEReF+e+OtVLuaaMSPw5LveaXHG1GB/8G1RR5MWhhSPz9gGvg9CwP8= X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5327 Archived-At: Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 17:37:26 -0000 Hi Mark,=0A= =0A= Please see inline. I have removed the comments where your suggested solutio= n is fine and I have nothing further to say.=0A= =0A= Nits/editorial comments:=0A= =0A= General:=0A= ---------=0A= =0A= QGEN_1:=0A= =0A= >> - The document uses =93as discussed in=94, =93as defined in=94, =93as de= scribed=94=0A= >> in terminology. It might be justified to use different terminology in=0A= >> some cases, but in general I suggest trying to use consistent terminolog= y.=0A= =0A= =85=0A= =0A= >The use of "as described in" is found in the standard boilerplate=0A= >copyright notice and the boilerplate Requirements language sections.=0A= >So, I have migrated from "discussed" to described" for consistentcy.=0A= =0A= That's good.=0A= =0A= =0A= Section 1:=0A= -----------=0A= =0A= Q1_1:=0A= =0A= >> The text says:=0A= >>=0A= >> =94[RFC5656] describes how elliptic curves are integrated in SSH, and th= is document reuses those protocol messages.=94=0A= >>=0A= >> =85and:=0A= >>=0A= >> =93This document describes how to implement key exchange based on Curve2= 5519 and Curve448 [RFC7748] in SSH.=94=0A= >>=0A= >> - It is unclear to me what =93integrated in SSH=94 means.=0A= >=0A= > The title of RFC 5656 is "Elliptic Curve Algorithm Integration in the Sec= ure Shell Transport Layer" and this Draft intents to augment the=0A= > Elliptic Curve methods defined there.=0A= >=0A= >>=0A= >> Does it mean that RFC 5656 describes the generic procedures for performi= ng SSH key exchanges using elliptic curves, or does it also=0A= >> cover other things?=0A= >=0A= > RFC5656 covers three specific constructions:=0A= >=0A= > a) Elliptic Curve Diffie-Hellman (ECDH),>=0A= > b) Elliptic Curve Menezes-Qu-Vanstone (ECMQV) key agreement, and=0A= > c) Elliptic Curve Digital Signature Algorithm (ECDSA).=0A= >=0A= > This draft does not cover the use of a digital signature algoirthm or app= ly the Curve25519 or Curve448 constructions to the use of ECMQV and=0A= > focuses entirely on ECDH key exchange extensions for a different construc= tion of elliptic curves.=0A= =0A= Would it be good to indicate that in a note?=0A= =0A= >> - I think the =93this document reuses those protocol messages=94 sounds = a=0A= >> little confusing because I don't know what =93those protocol message=94= =0A= >>refers to. Perhaps say something like =93reuses the protocol messages=0A= >> defined in that specification=94.=0A= >=0A= > This draft resuses the SSH_MSG_KEX_ECDH_INIT and SSH_MSG_KEX_ECDH_REPLY= =0A= > messages which apply to the ECDH construction as in in section 4 of this = draft.=0A= >=0A= > Does this paragraph work as a better replacement for the first paragraph= =0A= > of the introduction? Or, is it too detailed for a summary introduction?= =0A= >=0A= > Secure Shell (SSH) is a secure remote=0A= > login protocol. The key exchange protocol described in target=3D"RFC4253"/> supports an extensible set of methods. target=3D"RFC5656"/> defines how elliptic curves are integrated=0A= > into this extensible SSH framework, and this document reuses the=0A= > Elliptic Curve Diffie-Hellman (ECDH) key exchange protocol=0A= > messages defined in section 7.1 "ECDH Message Numbers" target=3D"RFC5656"/>.=0A= >=0A= > It seems a bit detailed to me for an introduction. Let me know if you=0A= > have any suggestions on a revision.=0A= =0A= I think the text looks good, and it is for sure a good clarification for a = non-security person like myself :)=0A= =0A= ---=0A= =0A= Q1_4:=0A= =0A= >> The text says:=0A= >>=0A= >> =93The Curve448 key exchange method is novel but similar in spirit,=94= =0A= >>=0A= >> - I don't know what this means, since there is now further explanation.= =0A= >=0A= > The paragraph now reads:=0A= >=0A= >This document describes how to implement key exchange based on=0A= >Curve25519 and Curve448 in SSH. For=0A= >Curve25519 with SHA-256 , the algorithm=0A= >described is equivalent to the privately defined algorithm=0A= >"curve25519-sha256@libssh.org", which at the time of publication=0A= > was implemented and widely deployed in libssh and OpenSSH. The=0A= > Curve448 key exchange method is similar but uses SHA-512 target=3D"RFC6234"/> to further separate it from the Curve25519=0A= > alternative.=0A= =0A= Looks good.=0A= =0A= > Would you rather that I use 'This document defines ...' here and in the= =0A= > abstract rather than 'This document describes ...' ? Please advise.=0A= =0A= Personally I would use "describe", but my main issue is being consistent - = no matter what word is used :)=0A= =0A= ---=0A= =0A= Q1_5:=0A= =0A= >> The text says:=0A= >>=0A= >>=0A= >> =93This document provide Curve25519 as the preferred choice, but=0A= >> suggests that the fall back option Curve448 is implemented to provid= e=0A= >> an hedge against unforeseen analytical advances against Curve25519= =0A= >> and SHA-256.=94=0A= >>=0A= >> - Is the only reason why one should implement Curve448 that something=0A= >> MAY happen to Curve25519 in the future?=0A= >=0A= >No, the Curve448 also has a stronger cryptographic security strength. If= =0A= >it becomes a requirement to use a minimum of 128 bits of security=0A= >strength, then Curve25519 may be rejected by some and thus the need to=0A= > provide for something stronger.=0A= =0A= Wouldn't it be enough to say that, instead of talking about unforeseen anal= ytical advances etc? I noted that the sec-dir reviewer had some comments on= that too.=0A= =0A= Please see below for suggested modified text.=0A= =0A= > Let me know if you which to have me remove the entire paragraph or not.= =0A= =0A= I think you could keep the paragraph, but instead say something like:=0A= =0A= =93This document provide Curve25519 as the preferred choice, but= =0A= suggests that the Curve448 is implemented in order to provide=0A= 128 bits of security strength, should that become a requirement.= =0A= =0A= At the time of writing this specification high-quality free impl= ementations=0A= of Curve25519 had been in deployed use for several years, while = Curve448=0A= implementations were slowly appearing, so it was accepted that a= doption =0A= of Curve448 would be slower." =0A= =0A= > Should I upload my updated draft-ietf-curdle-ssh-curves-10.xml or=0A= > do you have additional suggestions?=0A= =0A= I haven't seen the update draft yet, but if you are ok with my suggestions = you can go ahead to upload. If you are not ok with my suggestions, then let= me know :)=0A= =0A= Regards,=0A= =0A= Christer= From nobody Mon Aug 26 11:23:45 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B9CA120C3E; Mon, 26 Aug 2019 11:23:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net 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 aAXEIp_NER8y; Mon, 26 Aug 2019 11:23:28 -0700 (PDT) Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66602120B7C; Mon, 26 Aug 2019 11:23:28 -0700 (PDT) Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x7QIDteP021073; Mon, 26 Aug 2019 11:23:22 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=to : cc : subject : in-reply-to : references : from : mime-version : content-type : content-transfer-encoding : date : message-id; s=PPS1017; bh=K4JS3xbeHAnz53YSslIkTPGqv9EqtUt3p00064iznVk=; b=kGsCuYSiOYcbTgtRv/SRmXaKzkWk+XcIWKfO5PrIYfZqJ/NWbtDdTc+0Evw+DoSRhoNy 7MfferS3YqqWGXZ1UI9sgngdFd5n0kbQidCu8WYhFaF0IYBm1NkuAuQLjGNCdvONa59p RNwcKTpzrKYzp/O63M59iXA9J8WhsQHL5vUmmqOxFbyaa3AxywH7UwZXDg2pD7TZLtS7 crJtfyfIV+09vqGBHg0127Kk2bbj14gmBkamR8q7rMpCJrpzlrlVoksc9nxRLkZWRpO8 VGN7VzkHJUkBPz5SWWEBXD/Ojm8lPKM9piWDK5lavCeGsLTbiJisgVYtqLL5L6/7IuS2 5w== Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp2053.outbound.protection.outlook.com [104.47.40.53]) by mx0a-00273201.pphosted.com with ESMTP id 2ukne1j6k2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 26 Aug 2019 11:23:22 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fpqGpYnlV3NQ1rZH0RiEGzPFunMaP3Ze3ibfKMmefdkS1HTjIpN0G+yAxWAUq/V6f9eTezugR/sgDJKhym8uj/XH4J2mloj1dYVZcAqaM5fs9maiUIBJUDaybdUPl9rABzfyMZC/vVVsLfIUu5aLhf9MxQAbkxcfDShlnE2iTYMplnAxOlusadfT2I4sbYBaNDWvcEXqnL0JWf9/jjXysvaLUNMaBw3zIbUwwb2Zt/zma4ftQzL36nsFSfzJstlzg2Uc1EY9+gMyjSuyUja6cixlgLEmXIRgHTmPqCvmuSzGWZuIPMcl/6LSryPmsNt7wJEOclwNTQAPUx6YVW6Mjg== 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=K4JS3xbeHAnz53YSslIkTPGqv9EqtUt3p00064iznVk=; b=TXhYrxxbuYvNiw/yWAEHMvEcnJl95WSn62KUpvE5VPg8pgmcay3j3Zp0zxdlc1A4xCEu54ewy4gOoI5c+I0SvXBjRMKToVLJlahUS8EOVmG9vvdqmvHjLOjHl/SarwINMDrkLPR9S9zy3d4sEyPJY2SzTr+5QJf4N29rn20VnVI8O62V+BGA1thnpTyn6OTG04oq2n8Q1xeemaJSagYZ+vVvHH4hDfn0dfQTjpCWbwa91XqRZEBrSE6cS4u9ntpgO6Rr1dnhKBMJELTc/prZoGeklT5aKk4NKQ/PzoN4+Huwgb18Yo/L/p2YlUc9XQOk+QiVNOI0ZIeDq+AFkEQqPg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=softfail (sender ip is 66.129.239.12) smtp.rcpttodomain=ietf.org smtp.mailfrom=juniper.net; dmarc=fail (p=reject sp=reject pct=100) action=oreject header.from=juniper.net; dkim=none (message not signed); arc=none Received: from CO2PR05CA0100.namprd05.prod.outlook.com (2603:10b6:104:1::26) by BN7PR05MB4482.namprd05.prod.outlook.com (2603:10b6:406:ff::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.15; Mon, 26 Aug 2019 18:23:20 +0000 Received: from CO1NAM05FT041.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::205) by CO2PR05CA0100.outlook.office365.com (2603:10b6:104:1::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.11 via Frontend Transport; Mon, 26 Aug 2019 18:23:20 +0000 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender) Received: from P-EXFEND-EQX-01.jnpr.net (66.129.239.12) by CO1NAM05FT041.mail.protection.outlook.com (10.152.96.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2220.7 via Frontend Transport; Mon, 26 Aug 2019 18:23:19 +0000 Received: from P-EXBEND-EQX-03.jnpr.net (10.104.8.56) by P-EXFEND-EQX-01.jnpr.net (10.104.8.54) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 26 Aug 2019 11:23:19 -0700 Received: from P-EXBEND-EQX-02.jnpr.net (10.104.8.53) by P-EXBEND-EQX-03.jnpr.net (10.104.8.56) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 26 Aug 2019 11:23:18 -0700 Received: from p-mailhub01.juniper.net (10.104.20.6) by P-EXBEND-EQX-02.jnpr.net (10.104.8.53) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Mon, 26 Aug 2019 11:23:18 -0700 Received: from contrail-ubm16-mdb.svec1.juniper.net ([10.163.18.199]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id x7QINGii018589; Mon, 26 Aug 2019 11:23:17 -0700 (envelope-from mdb@juniper.net) To: Christer Holmberg CC: "gen-art@ietf.org" , "curdle@ietf.org" , "ietf@ietf.org" , "draft-ietf-curdle-ssh-curves.all@ietf.org" In-Reply-To: References: <156647523885.14827.16394888562228822662@ietfa.amsl.com>, <19556.1566836922@contrail-ubm16-mdb.svec1.juniper.net> Comments: In-reply-to: Christer Holmberg message dated "Mon, 26 Aug 2019 17:37:16 -0000." From: "Mark D. Baushke" X-Phone: +1 408 745-2952 (Office) X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1 X-Face: #8D_6URD2G%vC.hzU X-EXCLAIMER-MD-CONFIG: e3cb0ff2-54e7-4646-8a04-0dae4ac7b136 X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-HT: Tenant X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(4636009)(396003)(376002)(136003)(346002)(39860400002)(2980300002)(189003)(199004)(23676004)(86362001)(2906002)(117636001)(14444005)(5660300002)(50466002)(47776003)(478600001)(76176011)(70586007)(7696005)(2486003)(229853002)(53936002)(70206006)(54906003)(316002)(356004)(97876018)(8746002)(336012)(8936002)(6246003)(486006)(476003)(126002)(446003)(11346002)(426003)(81166006)(81156014)(8676002)(6916009)(50226002)(186003)(305945005)(26005)(4326008)(62816006); DIR:OUT; SFP:1102; SCL:1; SRVR:BN7PR05MB4482; H:P-EXFEND-EQX-01.jnpr.net; FPR:; SPF:SoftFail; LANG:en; PTR:InfoDomainNonexistent; MX:1; A:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 3ac260cf-9d02-4b6b-9401-08d72a5278c4 X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(4710121)(4711137)(1401327)(4618075)(2017052603328); SRVR:BN7PR05MB4482; X-MS-TrafficTypeDiagnostic: BN7PR05MB4482: X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:10000; X-Forefront-PRVS: 01415BB535 X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: A4ZhY8odA0lEwF9Iu0K1Xh7Ds5EZ6JzZldjzGgSP7QR7hBlrbNhmkP5BgkuGUyF9lOIOVNcOhemDQ5qLLMQjCjSgu5osAZS6QWuZSK3CcV4GRNQWxEy+oMH3cA7dQmkIoWBR2VyanVDRAGfbXehnXGkWNjnXGYWtbM5RHiP+q0vPgjQk/5L5UF66hU3N9dQKJZO7h4zNobBs3ToMe6/djb6hyz5jrGQZCeH7TTo72wBI/w5oSAgK55069s8VNJit4tfanG8QXX9n1sT/S41yWf5o3eBTV6LVv3QZYOymyyzERCeqH5hRDMRJlj4PD/sdbilTVk1jsnSkb3U3Bo2AaDD5JZK/raQKXoVZHUGmlZqopsKNT0VV7ikfgSoAkwWLjbZ0/t7q5Ph/wtdKHI1MP5qpIdVZicS/6QmpMeyQv4k= X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Aug 2019 18:23:19.6256 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 3ac260cf-9d02-4b6b-9401-08d72a5278c4 X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12]; Helo=[P-EXFEND-EQX-01.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR05MB4482 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-26_08:2019-08-26,2019-08-26 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 adultscore=0 mlxlogscore=999 malwarescore=0 bulkscore=0 suspectscore=0 impostorscore=0 phishscore=0 spamscore=0 mlxscore=0 lowpriorityscore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908260177 Archived-At: Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 18:23:30 -0000 Christer Holmberg writes: > Hi Mark, >=20 > Please see inline. I have removed the comments where your suggested > solution is fine and I have nothing further to say. I have done likewise. > Section 1: > ----------- >=20 > Q1_1: >=20 ...elided... > > RFC5656 covers three specific constructions: > > > > a) Elliptic Curve Diffie-Hellman (ECDH),> > > b) Elliptic Curve Menezes-Qu-Vanstone (ECMQV) key agreement, and > > c) Elliptic Curve Digital Signature Algorithm (ECDSA). > > > > This draft does not cover the use of a digital signature algoirthm > > or apply the Curve25519 or Curve448 constructions to the use of > > ECMQV and focuses entirely on ECDH key exchange extensions for a > > different construction of elliptic curves. >=20 > Would it be good to indicate that in a note? Possibly. I could add this as the final sentence to the first paragraph of the introduction: Other parts of , such as Elliptic Curve Menezes-Qu-Vanstone (ECMQV) key agreement, and Elliptic Curve Digital Signature Algorithm (ECDSA) are not considered in this document. ...elided... > > It seems a bit detailed to me for an introduction. Let me know if > > you have any suggestions on a revision. >=20 > I think the text looks good, and it is for sure a good clarification > for a non-security person like myself :) Okay, I will keep at as revised with the only other question being the addition of the sentence noted previously. ...elided... > Personally I would use "describe", but my main issue is being > consistent - no matter what word is used :) I will retain the 'This document defines...' text. I believe that there is a difference between defines and describes. The former is normative text and the latter is more informative. >=20 > --- >=20 > Q1_5: >=20 > >> The text says: > >> > >> > >> =E2=80=9CThis document provide Curve25519 as the preferred choice, = but > >> suggests that the fall back option Curve448 is implemented to prov= ide > >> an hedge against unforeseen analytical advances against Curve25519 > >> and SHA-256.=E2=80=9D > >> > >> - Is the only reason why one should implement Curve448 that something > >> MAY happen to Curve25519 in the future? > > > >No, the Curve448 also has a stronger cryptographic security strength. If > >it becomes a requirement to use a minimum of 128 bits of security > >strength, then Curve25519 may be rejected by some and thus the need to > > provide for something stronger. >=20 > Wouldn't it be enough to say that, instead of talking about unforeseen > analytical advances etc? I noted that the sec-dir reviewer had some > comments on that too. >=20 > Please see below for suggested modified text. >=20 > > Let me know if you which to have me remove the entire paragraph or not. >=20 > I think you could keep the paragraph, but instead say something like: >=20 > =E2=80=9CThis document provide Curve25519 as the preferred choi= ce, but > suggests that the Curve448 is implemented in order to provide > 128 bits of security strength, should that become a requiremen= t. >=20 > At the time of writing this specification high-quality free > implementations of Curve25519 had been in deployed use for > several years, while Curve448 implementations were slowly > appearing, so it was accepted that adoption of Curve448 > would be slower." >=20 > > Should I upload my updated draft-ietf-curdle-ssh-curves-10.xml or > > do you have additional suggestions? I have adopted your two paragraphs to replace the one paragraph that was previously present. > I haven't seen the update draft yet, but if you are ok with my > suggestions you can go ahead to upload. If you are not ok with my > suggestions, then let me know :) Only one questions remains as the last sentence of the first paragarph of the introduction. -- Mark From nobody Mon Aug 26 11:34:34 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D5B120C4C; Mon, 26 Aug 2019 11:34:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com 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 DMnbaQuJUldO; Mon, 26 Aug 2019 11:34:12 -0700 (PDT) Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00072.outbound.protection.outlook.com [40.107.0.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A603E120C4A; Mon, 26 Aug 2019 11:34:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Fa5jrsVlJHbhy5jqAoKsfr/qYURyWgPCojjoo2Rnef5CqHGdZVV2BmyVEk4ZZNmnJBEIBb0FwDuFK8A4hKKNrkuENvGnjHyIG2mATPuICIdhThs2oeqHb28bfVoXf9br/DlRo8be1rmRG8JHXugHxaTg5pbMHZjRyS1ya3PVpTH2Vdmg5J1hGmvc9v845T43r/pfPezpbOQi676rkWjKVrITPtYIGxsQZZbQp8mb7cz8vvS/hlSJW43dLg/x8P8DlSK3fXNOc6uC2DjVogGwuJrHtQunAE1Si5xTejWTIYL7acwiqvxWjVqU5PAwFQf11DOsHzxTHXAzAzPF9Mplyw== 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=iK4UnNFCta9/kn2yb0gLwFTZAJl4WxEvdR/JQ4Mck18=; b=JD+VVSOlGUhiJvn3tV2dy7uGM5CQ+6mdpV1dsTdTXNoJfQk43GYrK7pZ5dL2CCa5HcY42uoAZLsbH/19rrCiGCsqL/bpZKDf1V83DwYANcjFmhYCt0BFH2QLiuMXXD+cHb6RMv/QPwWRUhJnHVTZrQjb10+Yg9Ju9DLJ1OjLKZEbLIeO9FM2Z9+2IxaV/ZoL+nl/+5Bt5ccJnWhiX+Oyyf7TU10LYgIQt4Slu/eiRplDUUaRb1fWP5E72zrSnmvBbsixeXkvWfOMGvHHWvVqTreDJPVTE1wsnoSX7iWECAXhSctfLdtCCGdscSetO/4YlqAJhRuE/+bBECIKbs2DNQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iK4UnNFCta9/kn2yb0gLwFTZAJl4WxEvdR/JQ4Mck18=; b=jS4Zq9qDzEI5g0bWqRu/2hCuB/MG366HcAInbLQ7KXVd0N2sALfPqhuSE+YPrUjURZx/fhNboS7h/wdFJRwk+AmkOY01PP1ZK7aDCxrivf/9PDrmIq4HxyHgDJciAjZCDA4zxcYysngbAUoLAT8dMYK8mZwL6ktyQ9Slni9yecw= Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB4313.eurprd07.prod.outlook.com (20.176.167.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.11; Mon, 26 Aug 2019 18:34:07 +0000 Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::f0a1:2199:7816:ff8d]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::f0a1:2199:7816:ff8d%6]) with mapi id 15.20.2220.013; Mon, 26 Aug 2019 18:34:07 +0000 From: Christer Holmberg To: "Mark D. Baushke" CC: "gen-art@ietf.org" , "curdle@ietf.org" , "ietf@ietf.org" , "draft-ietf-curdle-ssh-curves.all@ietf.org" Thread-Topic: Genart last call review of draft-ietf-curdle-ssh-curves-09 Thread-Index: AQHVXCtcvr2YSg9UakaoGGnxJPuFPKcNqHWsgAAV3ACAAADEbQ== Date: Mon, 26 Aug 2019 18:34:06 +0000 Message-ID: References: <156647523885.14827.16394888562228822662@ietfa.amsl.com>, <19556.1566836922@contrail-ubm16-mdb.svec1.juniper.net> , <22345.1566843796@contrail-ubm16-mdb.svec1.juniper.net> In-Reply-To: <22345.1566843796@contrail-ubm16-mdb.svec1.juniper.net> 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=christer.holmberg@ericsson.com; x-originating-ip: [79.134.118.162] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: ecf40a91-f03d-4715-47e9-08d72a53fa99 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600166)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:HE1PR07MB4313; x-ms-traffictypediagnostic: HE1PR07MB4313: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 01415BB535 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(376002)(39860400002)(346002)(396003)(189003)(199004)(476003)(14454004)(478600001)(66556008)(66066001)(76116006)(66946007)(66446008)(64756008)(54906003)(66476007)(44832011)(33656002)(19627405001)(99286004)(1941001)(71190400001)(71200400001)(316002)(486006)(229853002)(6506007)(7736002)(86362001)(6246003)(6436002)(8936002)(4326008)(105004)(81166006)(81156014)(8676002)(74316002)(5660300002)(25786009)(446003)(6916009)(186003)(26005)(2906002)(102836004)(6116002)(3846002)(11346002)(53936002)(7696005)(9686003)(54896002)(14444005)(52536014)(55016002)(76176011)(256004); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB4313; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: C4iAqUKd9jVybrDaXrc2LYYSq6fvpmVKYxD9TwKkAog2BUoA0Rd5qQQAal/1pcf6Vbv2gAgIskacPq67ECmL+9Fsd7m/c9ji5IAoHDjdibORuxZcA9+cP2eY+y0BrBDgu4KS9Hq/bRgFVbXtFUXVco3u6ocSGoAxdvi2BkadKYPvhvH3h54Rx4ftVsF8DTcjLCxWPLGCUk6cSkupqTWEflDqFNGKhgUeV04aKdbNzRLRe5VNMQIvnzuUjZKkOLoZdEzlld0413bgQv5oKlEaWJq29NbgD18d2+TlFo9yId/TnhTCZ1a+0TTMOP9rcFapRSkIpIR2YmPJyxwZI8wWn79lalHdUsp2SFLUcJ204ytAx5wA6MpyFcsBrrBUAH8VzNaFKPrvevkFx4yRB3UlhC43LzOGKdo4Uq0fYEtbAp4= x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3161966302E5C1AB1901874E93A10HE1PR07MB3161eurp_" MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-Network-Message-Id: ecf40a91-f03d-4715-47e9-08d72a53fa99 X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Aug 2019 18:34:06.9257 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: 0n8qGH+X96peq28NfjZ2H1KL762YKnEwVIPIx/4TSj91KWsgPz8dXx9uM2D3RO11L91ThuO33D/m0F9CvYuPjg284LsQVpFoTuqLlkHtDog= X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4313 Archived-At: Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 18:34:18 -0000 --_000_HE1PR07MB3161966302E5C1AB1901874E93A10HE1PR07MB3161eurp_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 DQpIaSBNYXJrLA0KDQpTZWN0aW9uIDE6DQotLS0tLS0tLS0tLQ0KDQo+PiBRMV8xOg0KPj4NCi4u LmVsaWRlZC4uLg0KPj4+IFJGQzU2NTYgY292ZXJzIHRocmVlIHNwZWNpZmljIGNvbnN0cnVjdGlv bnM6DQo+Pj4NCj4+PiAgIGEpIEVsbGlwdGljIEN1cnZlIERpZmZpZS1IZWxsbWFuIChFQ0RIKSw+ DQo+Pj4gICBiKSBFbGxpcHRpYyBDdXJ2ZSBNZW5lemVzLVF1LVZhbnN0b25lIChFQ01RVikga2V5 IGFncmVlbWVudCwgYW5kDQo+Pj4gICBjKSBFbGxpcHRpYyBDdXJ2ZSBEaWdpdGFsIFNpZ25hdHVy ZSBBbGdvcml0aG0gKEVDRFNBKS4NCj4+Pg0KPj4+IFRoaXMgZHJhZnQgZG9lcyBub3QgY292ZXIg dGhlIHVzZSBvZiBhIGRpZ2l0YWwgc2lnbmF0dXJlIGFsZ29pcnRobQ0KPj4+IG9yIGFwcGx5IHRo ZSBDdXJ2ZTI1NTE5IG9yIEN1cnZlNDQ4IGNvbnN0cnVjdGlvbnMgdG8gdGhlIHVzZSBvZg0KPj4+ IEVDTVFWIGFuZCBmb2N1c2VzIGVudGlyZWx5IG9uIEVDREgga2V5IGV4Y2hhbmdlIGV4dGVuc2lv bnMgZm9yIGENCj4+PiBkaWZmZXJlbnQgY29uc3RydWN0aW9uIG9mIGVsbGlwdGljIGN1cnZlcy4N Cj4+DQo+PiBXb3VsZCBpdCBiZSBnb29kIHRvIGluZGljYXRlIHRoYXQgaW4gYSBub3RlPw0KPg0K PiBQb3NzaWJseS4gSSBjb3VsZCBhZGQgdGhpcyBhcyB0aGUgZmluYWwgc2VudGVuY2UgdG8gdGhl IGZpcnN0IHBhcmFncmFwaA0KPiBvZiB0aGUgaW50cm9kdWN0aW9uOg0KPg0KPiAgICAgICAgT3Ro ZXIgcGFydHMgb2YgPHhyZWYgdGFyZ2V0PSJSRkM1NjU2Ii8+LCBzdWNoIGFzIEVsbGlwdGljIEN1 cnZlDQo+ICAgICAgICBNZW5lemVzLVF1LVZhbnN0b25lIChFQ01RVikga2V5IGFncmVlbWVudCwg YW5kIEVsbGlwdGljIEN1cnZlDQo+ICAgICAgIERpZ2l0YWwgU2lnbmF0dXJlIEFsZ29yaXRobSAo RUNEU0EpIGFyZSBub3QgY29uc2lkZXJlZCBpbiB0aGlzDQo+ICAgICAgICBkb2N1bWVudC4NCg0K TG9va3MgZ29vZC4NCg0KLi4uZWxpZGVkLi4uDQoNCj4+PiBJdCBzZWVtcyBhIGJpdCBkZXRhaWxl ZCB0byBtZSBmb3IgYW4gaW50cm9kdWN0aW9uLiBMZXQgbWUga25vdyBpZg0KPj4+IHlvdSBoYXZl IGFueSBzdWdnZXN0aW9ucyBvbiBhIHJldmlzaW9uLg0KPj4NCj4+IEkgdGhpbmsgdGhlIHRleHQg bG9va3MgZ29vZCwgYW5kIGl0IGlzIGZvciBzdXJlIGEgZ29vZCBjbGFyaWZpY2F0aW9uDQo+PiBm b3IgYSBub24tc2VjdXJpdHkgcGVyc29uIGxpa2UgbXlzZWxmIDopDQo+DQo+IE9rYXksIEkgd2ls bCBrZWVwIGF0IGFzIHJldmlzZWQgd2l0aCB0aGUgb25seSBvdGhlciBxdWVzdGlvbiBiZWluZyB0 aGUNCj4gYWRkaXRpb24gb2YgdGhlIHNlbnRlbmNlIG5vdGVkIHByZXZpb3VzbHkuDQoNCk9rLg0K DQouLi5lbGlkZWQuLi4NCg0KPj4gUGVyc29uYWxseSBJIHdvdWxkIHVzZSAiZGVzY3JpYmUiLCBi dXQgbXkgbWFpbiBpc3N1ZSBpcyBiZWluZw0KPj4gY29uc2lzdGVudCAtIG5vIG1hdHRlciB3aGF0 IHdvcmQgaXMgdXNlZCA6KQ0KPg0KPiBJIHdpbGwgcmV0YWluIHRoZSAnVGhpcyBkb2N1bWVudCBk ZWZpbmVzLi4uJyB0ZXh0Lg0KPg0KPiBJIGJlbGlldmUgdGhhdCB0aGVyZSBpcyBhIGRpZmZlcmVu Y2UgYmV0d2VlbiBkZWZpbmVzIGFuZCBkZXNjcmliZXMuIFRoZQ0KPiBmb3JtZXIgaXMgbm9ybWF0 aXZlIHRleHQgYW5kIHRoZSBsYXR0ZXIgaXMgbW9yZSBpbmZvcm1hdGl2ZS4NCg0KU3VyZSwgYW5k IGlmIHlvdSB0aGluayB0aGVyZSBhcmUgc2l0dWF0aW9ucyB3aGVyZSB5b3Ugd2FudCB0byB1c2Ug Ym90aCwgdGhhdCdzIGZpbmUuIEJ1dCwgb2Z0ZW4gcGVvcGxlIGp1c3QgdXNlIHRoZSB3b3JkIHRo YXQgY29tZXMgdG8gdGhlaXIgbWluZCB3aGVuIHdyaXRpbmcgKG9yIGFkZGluZyB0ZXh0IHdyaXR0 ZW4gYnkgc29tZW9uZSBlbHNlKSwgYW5kIHRoYXQgY2F1c2VzIHRoZSBpbmNvbnNpc3RlbmNlIGlu IHRlcm1pbm9sb2d5Lg0KDQotLS0NCg0KUTFfNToNCg0KPj4+PiBUaGUgdGV4dCBzYXlzOg0KPj4+ Pg0KPj4+Pg0KPj4+PiAgICDigJxUaGlzIGRvY3VtZW50IHByb3ZpZGUgQ3VydmUyNTUxOSBhcyB0 aGUgcHJlZmVycmVkIGNob2ljZSwgYnV0DQo+Pj4+ICAgICBzdWdnZXN0cyB0aGF0IHRoZSBmYWxs IGJhY2sgb3B0aW9uIEN1cnZlNDQ4IGlzIGltcGxlbWVudGVkIHRvIHByb3ZpZGUNCj4+Pj4gICAg IGFuIGhlZGdlIGFnYWluc3QgdW5mb3Jlc2VlbiBhbmFseXRpY2FsIGFkdmFuY2VzIGFnYWluc3Qg Q3VydmUyNTUxOQ0KPj4+PiAgICAgYW5kIFNIQS0yNTYu4oCdDQo+Pj4+DQo+Pj4+IC0gSXMgdGhl IG9ubHkgcmVhc29uIHdoeSBvbmUgc2hvdWxkIGltcGxlbWVudCBDdXJ2ZTQ0OCB0aGF0IHNvbWV0 aGluZw0KPj4+PiAgICBNQVkgaGFwcGVuIHRvIEN1cnZlMjU1MTkgaW4gdGhlIGZ1dHVyZT8NCj4+ Pg0KPj4+Tm8sIHRoZSBDdXJ2ZTQ0OCBhbHNvIGhhcyBhIHN0cm9uZ2VyIGNyeXB0b2dyYXBoaWMg c2VjdXJpdHkgc3RyZW5ndGguIElmDQo+Pj5pdCBiZWNvbWVzIGEgcmVxdWlyZW1lbnQgdG8gdXNl IGEgbWluaW11bSBvZiAxMjggYml0cyBvZiBzZWN1cml0eQ0KPj4+c3RyZW5ndGgsIHRoZW4gQ3Vy dmUyNTUxOSBtYXkgYmUgcmVqZWN0ZWQgYnkgc29tZSBhbmQgdGh1cyB0aGUgbmVlZCB0bw0KPj4+ IHByb3ZpZGUgZm9yIHNvbWV0aGluZyBzdHJvbmdlci4NCj4+DQo+PiBXb3VsZG4ndCBpdCBiZSBl bm91Z2ggdG8gc2F5IHRoYXQsIGluc3RlYWQgb2YgdGFsa2luZyBhYm91dCB1bmZvcmVzZWVuDQo+ PiBhbmFseXRpY2FsIGFkdmFuY2VzIGV0Yz8gSSBub3RlZCB0aGF0IHRoZSBzZWMtZGlyIHJldmll d2VyIGhhZCBzb21lDQo+PiBjb21tZW50cyBvbiB0aGF0IHRvby4NCj4+DQo+PiBQbGVhc2Ugc2Vl IGJlbG93IGZvciBzdWdnZXN0ZWQgbW9kaWZpZWQgdGV4dC4NCj4+DQo+Pj4gTGV0IG1lIGtub3cg aWYgeW91IHdoaWNoIHRvIGhhdmUgbWUgcmVtb3ZlIHRoZSBlbnRpcmUgcGFyYWdyYXBoIG9yIG5v dC4NCj4+DQo+PiBJIHRoaW5rIHlvdSBjb3VsZCBrZWVwIHRoZSBwYXJhZ3JhcGgsIGJ1dCBpbnN0 ZWFkIHNheSBzb21ldGhpbmcgbGlrZToNCj4+DQo+PiAgICAgICAgICAg4oCcVGhpcyBkb2N1bWVu dCBwcm92aWRlIEN1cnZlMjU1MTkgYXMgdGhlIHByZWZlcnJlZCBjaG9pY2UsIGJ1dA0KPj4gICAg ICAgICAgICBzdWdnZXN0cyB0aGF0IHRoZSBDdXJ2ZTQ0OCBpcyBpbXBsZW1lbnRlZCBpbiBvcmRl ciB0byBwcm92aWRlDQo+PiAgICAgICAgICAgIDEyOCBiaXRzIG9mIHNlY3VyaXR5IHN0cmVuZ3Ro LCBzaG91bGQgdGhhdCBiZWNvbWUgYSByZXF1aXJlbWVudC4NCj4+DQo+PiAgICAgICAgICAgIEF0 IHRoZSB0aW1lIG9mIHdyaXRpbmcgdGhpcyBzcGVjaWZpY2F0aW9uIGhpZ2gtcXVhbGl0eSBmcmVl DQo+PiAgICAgICAgICAgIGltcGxlbWVudGF0aW9ucyBvZiBDdXJ2ZTI1NTE5IGhhZCBiZWVuIGlu IGRlcGxveWVkIHVzZSBmb3INCj4+ICAgICAgICAgICAgc2V2ZXJhbCB5ZWFycywgd2hpbGUgQ3Vy dmU0NDggaW1wbGVtZW50YXRpb25zIHdlcmUgc2xvd2x5DQo+PiAgICAgICAgICAgIGFwcGVhcmlu Zywgc28gaXQgd2FzIGFjY2VwdGVkIHRoYXQgYWRvcHRpb24gb2YgQ3VydmU0NDgNCj4+ICAgICAg ICAgICAgd291bGQgYmUgc2xvd2VyLiINCj4+DQo+Pj4gU2hvdWxkIEkgdXBsb2FkIG15IHVwZGF0 ZWQgZHJhZnQtaWV0Zi1jdXJkbGUtc3NoLWN1cnZlcy0xMC54bWwgb3INCj4+PiBkbyB5b3UgaGF2 ZSBhZGRpdGlvbmFsIHN1Z2dlc3Rpb25zPw0KPg0KPiBJIGhhdmUgYWRvcHRlZCB5b3VyIHR3byBw YXJhZ3JhcGhzIHRvIHJlcGxhY2UgdGhlIG9uZSBwYXJhZ3JhcGggdGhhdCB3YXMNCj4gcHJldmlv dXNseSBwcmVzZW50Lg0KPg0KPj4gSSBoYXZlbid0IHNlZW4gdGhlIHVwZGF0ZSBkcmFmdCB5ZXQs IGJ1dCBpZiB5b3UgYXJlIG9rIHdpdGggbXkNCj4+IHN1Z2dlc3Rpb25zIHlvdSBjYW4gZ28gYWhl YWQgdG8gdXBsb2FkLiBJZiB5b3UgYXJlIG5vdCBvayB3aXRoIG15DQo+PiBzdWdnZXN0aW9ucywg dGhlbiBsZXQgbWUga25vdyA6KQ0KPg0KPiBPbmx5IG9uZSBxdWVzdGlvbnMgcmVtYWlucyBhcyB0 aGUgbGFzdCBzZW50ZW5jZSBvZiB0aGUgZmlyc3QgcGFyYWdhcnBoDQo+IG9mIHRoZSBpbnRyb2R1 Y3Rpb24uDQoNClRoZSB0ZXh0IHlvdSBzdWdnZXN0ZWQgbG9va3MgZ29vZC4NCg0KU28sIGFzIGZh ciBhcyBJJ20gY29uY2VybmVkLCBnbyBhaGVhZCBhbmQgbWFrZSB0aGUgY2hhbmdlIGFuZCBzdWJt aXQgdGhlIC0xMCB2ZXJzaW9uIPCfmYINCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K --_000_HE1PR07MB3161966302E5C1AB1901874E93A10HE1PR07MB3161eurp_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyIgc3R5bGU9 ImRpc3BsYXk6bm9uZTsiPiBQIHttYXJnaW4tdG9wOjA7bWFyZ2luLWJvdHRvbTowO30gPC9zdHls ZT4NCjwvaGVhZD4NCjxib2R5IGRpcj0ibHRyIj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwg MCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLEFyaWFsLEhlbHZldGljYSxzYW5zLXNlcmlmOyBm b250LXNpemU6IDEycHQ7Ij4NCjxmb250IHNpemU9IjIiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6 MTFwdCI+PGJyPg0KPC9zcGFuPjwvZm9udD48L2Rpdj4NCjxkaXY+DQo8ZGl2IGNsYXNzPSJCb2R5 RnJhZ21lbnQiPjxmb250IHNpemU9IjIiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTFwdCI+DQo8 ZGl2IGNsYXNzPSJQbGFpblRleHQiPkhpIE1hcmssPGJyPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNs YXNzPSJQbGFpblRleHQiPlNlY3Rpb24gMTo8YnI+DQotLS0tLS0tLS0tLTxicj4NCiZuYnNwOzxi cj4NCiZndDsmZ3Q7IFExXzE6PGJyPg0KJmd0OyZndDsgPGJyPg0KLi4uZWxpZGVkLi4uPGJyPg0K Jmd0OyZndDsmZ3Q7IFJGQzU2NTYgY292ZXJzIHRocmVlIHNwZWNpZmljIGNvbnN0cnVjdGlvbnM6 PGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jm5ic3A7Jm5ic3A7IGEpIEVsbGlw dGljIEN1cnZlIERpZmZpZS1IZWxsbWFuIChFQ0RIKSwmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jm5i c3A7Jm5ic3A7IGIpIEVsbGlwdGljIEN1cnZlIE1lbmV6ZXMtUXUtVmFuc3RvbmUgKEVDTVFWKSBr ZXkgYWdyZWVtZW50LCBhbmQ8YnI+DQomZ3Q7Jmd0OyZndDsmbmJzcDsmbmJzcDsgYykgRWxsaXB0 aWMgQ3VydmUgRGlnaXRhbCBTaWduYXR1cmUgQWxnb3JpdGhtIChFQ0RTQSkuPGJyPg0KJmd0OyZn dDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IFRoaXMgZHJhZnQgZG9lcyBub3QgY292ZXIgdGhlIHVz ZSBvZiBhIGRpZ2l0YWwgc2lnbmF0dXJlIGFsZ29pcnRobTxicj4NCiZndDsmZ3Q7Jmd0OyBvciBh cHBseSB0aGUgQ3VydmUyNTUxOSBvciBDdXJ2ZTQ0OCBjb25zdHJ1Y3Rpb25zIHRvIHRoZSB1c2Ug b2Y8YnI+DQomZ3Q7Jmd0OyZndDsgRUNNUVYgYW5kIGZvY3VzZXMgZW50aXJlbHkgb24gRUNESCBr ZXkgZXhjaGFuZ2UgZXh0ZW5zaW9ucyBmb3IgYTxicj4NCiZndDsmZ3Q7Jmd0OyBkaWZmZXJlbnQg Y29uc3RydWN0aW9uIG9mIGVsbGlwdGljIGN1cnZlcy48YnI+DQomZ3Q7Jmd0OyA8YnI+DQomZ3Q7 Jmd0OyBXb3VsZCBpdCBiZSBnb29kIHRvIGluZGljYXRlIHRoYXQgaW4gYSBub3RlPzxicj4NCiZn dDs8YnI+DQomZ3Q7IFBvc3NpYmx5LiBJIGNvdWxkIGFkZCB0aGlzIGFzIHRoZSBmaW5hbCBzZW50 ZW5jZSB0byB0aGUgZmlyc3QgcGFyYWdyYXBoPGJyPg0KJmd0OyBvZiB0aGUgaW50cm9kdWN0aW9u Ojxicj4NCiZndDs8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Jm5ic3A7IE90aGVyIHBh cnRzIG9mICZsdDt4cmVmIHRhcmdldD0mcXVvdDtSRkM1NjU2JnF1b3Q7LyZndDssIHN1Y2ggYXMg RWxsaXB0aWMgQ3VydmU8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7Jm5ic3A7IE1lbmV6 ZXMtUXUtVmFuc3RvbmUgKEVDTVFWKSBrZXkgYWdyZWVtZW50LCBhbmQgRWxsaXB0aWMgQ3VydmU8 YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IERpZ2l0YWwgU2lnbmF0dXJlIEFsZ29yaXRo bSAoRUNEU0EpIGFyZSBub3QgY29uc2lkZXJlZCBpbiB0aGlzPGJyPg0KJmd0OyAmbmJzcDsgJm5i c3A7ICZuYnNwOyZuYnNwOyBkb2N1bWVudC48YnI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9 IlBsYWluVGV4dCI+TG9va3MgZ29vZC48L2Rpdj4NCjxkaXYgY2xhc3M9IlBsYWluVGV4dCI+PGJy Pg0KLi4uZWxpZGVkLi4uPGJyPg0KPGJyPg0KJmd0OyZndDsmZ3Q7IEl0IHNlZW1zIGEgYml0IGRl dGFpbGVkIHRvIG1lIGZvciBhbiBpbnRyb2R1Y3Rpb24uIExldCBtZSBrbm93IGlmPGJyPg0KJmd0 OyZndDsmZ3Q7IHlvdSBoYXZlIGFueSBzdWdnZXN0aW9ucyBvbiBhIHJldmlzaW9uLjxicj4NCiZn dDsmZ3Q7IDxicj4NCiZndDsmZ3Q7IEkgdGhpbmsgdGhlIHRleHQgbG9va3MgZ29vZCwgYW5kIGl0 IGlzIGZvciBzdXJlIGEgZ29vZCBjbGFyaWZpY2F0aW9uPGJyPg0KJmd0OyZndDsgZm9yIGEgbm9u LXNlY3VyaXR5IHBlcnNvbiBsaWtlIG15c2VsZiA6KTxicj4NCiZndDs8YnI+DQomZ3Q7IE9rYXks IEkgd2lsbCBrZWVwIGF0IGFzIHJldmlzZWQgd2l0aCB0aGUgb25seSBvdGhlciBxdWVzdGlvbiBi ZWluZyB0aGU8YnI+DQomZ3Q7IGFkZGl0aW9uIG9mIHRoZSBzZW50ZW5jZSBub3RlZCBwcmV2aW91 c2x5Ljxicj4NCjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iUGxhaW5UZXh0Ij5Pay48L2Rpdj4N CjxkaXYgY2xhc3M9IlBsYWluVGV4dCI+PGJyPg0KLi4uZWxpZGVkLi4uPGJyPg0KPGJyPg0KJmd0 OyZndDsgUGVyc29uYWxseSBJIHdvdWxkIHVzZSAmcXVvdDtkZXNjcmliZSZxdW90OywgYnV0IG15 IG1haW4gaXNzdWUgaXMgYmVpbmc8YnI+DQomZ3Q7Jmd0OyBjb25zaXN0ZW50IC0gbm8gbWF0dGVy IHdoYXQgd29yZCBpcyB1c2VkIDopPGJyPg0KJmd0Ozxicj4NCiZndDsgSSB3aWxsIHJldGFpbiB0 aGUgJ1RoaXMgZG9jdW1lbnQgZGVmaW5lcy4uLicgdGV4dC48YnI+DQomZ3Q7PGJyPg0KJmd0OyBJ IGJlbGlldmUgdGhhdCB0aGVyZSBpcyBhIGRpZmZlcmVuY2UgYmV0d2VlbiBkZWZpbmVzIGFuZCBk ZXNjcmliZXMuIFRoZTxicj4NCiZndDsgZm9ybWVyIGlzIG5vcm1hdGl2ZSB0ZXh0IGFuZCB0aGUg bGF0dGVyIGlzIG1vcmUgaW5mb3JtYXRpdmUuPGJyPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNz PSJQbGFpblRleHQiPlN1cmUsIGFuZCBpZiB5b3UgdGhpbmsgdGhlcmUgYXJlIHNpdHVhdGlvbnMg d2hlcmUgeW91IHdhbnQgdG8gdXNlIGJvdGgsIHRoYXQncyBmaW5lLiBCdXQsIG9mdGVuIHBlb3Bs ZSBqdXN0IHVzZSB0aGUgd29yZCB0aGF0IGNvbWVzIHRvIHRoZWlyIG1pbmQgd2hlbiB3cml0aW5n IChvciBhZGRpbmcgdGV4dCB3cml0dGVuIGJ5IHNvbWVvbmUgZWxzZSksIGFuZCB0aGF0IGNhdXNl cyB0aGUgaW5jb25zaXN0ZW5jZQ0KIGluIHRlcm1pbm9sb2d5LjwvZGl2Pg0KPGRpdiBjbGFzcz0i UGxhaW5UZXh0Ij48YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IlBsYWluVGV4dCI+LS0tPGJyPg0K Jm5ic3A7PGJyPg0KUTFfNTo8YnI+DQombmJzcDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IFRoZSB0 ZXh0IHNheXM6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDs8YnI+ DQomZ3Q7Jmd0OyZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7IOKAnFRoaXMgZG9jdW1lbnQgcHJv dmlkZSBDdXJ2ZTI1NTE5IGFzIHRoZSBwcmVmZXJyZWQgY2hvaWNlLCBidXQ8YnI+DQomZ3Q7Jmd0 OyZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHN1Z2dlc3RzIHRoYXQgdGhlIGZhbGwg YmFjayBvcHRpb24gQ3VydmU0NDggaXMgaW1wbGVtZW50ZWQgdG8gcHJvdmlkZTxicj4NCiZndDsm Z3Q7Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgYW4gaGVkZ2UgYWdhaW5zdCB1bmZv cmVzZWVuIGFuYWx5dGljYWwgYWR2YW5jZXMgYWdhaW5zdCBDdXJ2ZTI1NTE5PGJyPg0KJmd0OyZn dDsmZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBhbmQgU0hBLTI1Ni7igJ08YnI+DQom Z3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyAtIElzIHRoZSBvbmx5IHJlYXNv biB3aHkgb25lIHNob3VsZCBpbXBsZW1lbnQgQ3VydmU0NDggdGhhdCBzb21ldGhpbmc8YnI+DQom Z3Q7Jmd0OyZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7IE1BWSBoYXBwZW4gdG8gQ3VydmUyNTUx OSBpbiB0aGUgZnV0dXJlPzxicj4NCiZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0O05vLCB0 aGUgQ3VydmU0NDggYWxzbyBoYXMgYSBzdHJvbmdlciBjcnlwdG9ncmFwaGljIHNlY3VyaXR5IHN0 cmVuZ3RoLiBJZjxicj4NCiZndDsmZ3Q7Jmd0O2l0IGJlY29tZXMgYSByZXF1aXJlbWVudCB0byB1 c2UgYSBtaW5pbXVtIG9mIDEyOCBiaXRzIG9mIHNlY3VyaXR5PGJyPg0KJmd0OyZndDsmZ3Q7c3Ry ZW5ndGgsIHRoZW4gQ3VydmUyNTUxOSBtYXkgYmUgcmVqZWN0ZWQgYnkgc29tZSBhbmQgdGh1cyB0 aGUgbmVlZCB0bzxicj4NCiZndDsmZ3Q7Jmd0OyBwcm92aWRlIGZvciBzb21ldGhpbmcgc3Ryb25n ZXIuPGJyPg0KJmd0OyZndDsgPGJyPg0KJmd0OyZndDsgV291bGRuJ3QgaXQgYmUgZW5vdWdoIHRv IHNheSB0aGF0LCBpbnN0ZWFkIG9mIHRhbGtpbmcgYWJvdXQgdW5mb3Jlc2Vlbjxicj4NCiZndDsm Z3Q7IGFuYWx5dGljYWwgYWR2YW5jZXMgZXRjPyBJIG5vdGVkIHRoYXQgdGhlIHNlYy1kaXIgcmV2 aWV3ZXIgaGFkIHNvbWU8YnI+DQomZ3Q7Jmd0OyBjb21tZW50cyBvbiB0aGF0IHRvby48YnI+DQom Z3Q7Jmd0OyA8YnI+DQomZ3Q7Jmd0OyBQbGVhc2Ugc2VlIGJlbG93IGZvciBzdWdnZXN0ZWQgbW9k aWZpZWQgdGV4dC48YnI+DQomZ3Q7Jmd0OyA8YnI+DQomZ3Q7Jmd0OyZndDsgTGV0IG1lIGtub3cg aWYgeW91IHdoaWNoIHRvIGhhdmUgbWUgcmVtb3ZlIHRoZSBlbnRpcmUgcGFyYWdyYXBoIG9yIG5v dC48YnI+DQomZ3Q7Jmd0OyA8YnI+DQomZ3Q7Jmd0OyBJIHRoaW5rIHlvdSBjb3VsZCBrZWVwIHRo ZSBwYXJhZ3JhcGgsIGJ1dCBpbnN0ZWFkIHNheSBzb21ldGhpbmcgbGlrZTo8YnI+DQomZ3Q7Jmd0 OyA8YnI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyDigJxUaGlzIGRvY3VtZW50IHByb3ZpZGUgQ3VydmUyNTUxOSBh cyB0aGUgcHJlZmVycmVkIGNob2ljZSwgYnV0PGJyPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgc3VnZ2Vz dHMgdGhhdCB0aGUgQ3VydmU0NDggaXMgaW1wbGVtZW50ZWQgaW4gb3JkZXIgdG8gcHJvdmlkZTxi cj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDEyOCBiaXRzIG9mIHNlY3VyaXR5IHN0cmVuZ3RoLCBzaG91 bGQgdGhhdCBiZWNvbWUgYSByZXF1aXJlbWVudC48YnI+DQomZ3Q7Jmd0OyA8YnI+DQomZ3Q7Jmd0 OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyBBdCB0aGUgdGltZSBvZiB3cml0aW5nIHRoaXMgc3BlY2lmaWNhdGlvbiBoaWdo LXF1YWxpdHkgZnJlZTxicj4NCiZndDsmZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGltcGxlbWVudGF0aW9ucyBvZiBD dXJ2ZTI1NTE5IGhhZCBiZWVuIGluIGRlcGxveWVkIHVzZSBmb3I8YnI+DQomZ3Q7Jmd0OyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyBzZXZlcmFsIHllYXJzLCB3aGlsZSBDdXJ2ZTQ0OCBpbXBsZW1lbnRhdGlvbnMgd2VyZSBz bG93bHk8YnI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBhcHBlYXJpbmcsIHNvIGl0IHdhcyBhY2NlcHRl ZCB0aGF0IGFkb3B0aW9uIG9mIEN1cnZlNDQ4PGJyPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgd291bGQg YmUgc2xvd2VyLiZxdW90Ozxicj4NCiZndDsmZ3Q7IDxicj4NCiZndDsmZ3Q7Jmd0OyBTaG91bGQg SSB1cGxvYWQgbXkgdXBkYXRlZCBkcmFmdC1pZXRmLWN1cmRsZS1zc2gtY3VydmVzLTEwLnhtbCBv cjxicj4NCiZndDsmZ3Q7Jmd0OyBkbyB5b3UgaGF2ZSBhZGRpdGlvbmFsIHN1Z2dlc3Rpb25zPzxi cj4NCiZndDs8YnI+DQomZ3Q7IEkgaGF2ZSBhZG9wdGVkIHlvdXIgdHdvIHBhcmFncmFwaHMgdG8g cmVwbGFjZSB0aGUgb25lIHBhcmFncmFwaCB0aGF0IHdhczxicj4NCiZndDsgcHJldmlvdXNseSBw cmVzZW50Ljxicj4NCiZndDs8YnI+DQomZ3Q7Jmd0OyBJIGhhdmVuJ3Qgc2VlbiB0aGUgdXBkYXRl IGRyYWZ0IHlldCwgYnV0IGlmIHlvdSBhcmUgb2sgd2l0aCBteTxicj4NCiZndDsmZ3Q7IHN1Z2dl c3Rpb25zIHlvdSBjYW4gZ28gYWhlYWQgdG8gdXBsb2FkLiBJZiB5b3UgYXJlIG5vdCBvayB3aXRo IG15PGJyPg0KJmd0OyZndDsgc3VnZ2VzdGlvbnMsIHRoZW4gbGV0IG1lIGtub3cgOik8YnI+DQom Z3Q7PGJyPg0KJmd0OyBPbmx5IG9uZSBxdWVzdGlvbnMgcmVtYWlucyBhcyB0aGUgbGFzdCBzZW50 ZW5jZSBvZiB0aGUgZmlyc3QgcGFyYWdhcnBoPGJyPg0KJmd0OyBvZiB0aGUgaW50cm9kdWN0aW9u LjwvZGl2Pg0KPGRpdiBjbGFzcz0iUGxhaW5UZXh0Ij48YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9 IlBsYWluVGV4dCI+VGhlIHRleHQgeW91IHN1Z2dlc3RlZCBsb29rcyBnb29kLjwvZGl2Pg0KPGRp diBjbGFzcz0iUGxhaW5UZXh0Ij48YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IlBsYWluVGV4dCI+ U28sIGFzIGZhciBhcyBJJ20gY29uY2VybmVkLCBnbyBhaGVhZCBhbmQgbWFrZSB0aGUgY2hhbmdl IGFuZCBzdWJtaXQgdGhlIC0xMCB2ZXJzaW9uDQo8c3BhbiBpZD0i8J+ZgiI+8J+Zgjwvc3Bhbj48 L2Rpdj4NCjxkaXYgY2xhc3M9IlBsYWluVGV4dCI+PGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJQ bGFpblRleHQiPlJlZ2FyZHMsPC9kaXY+DQo8ZGl2IGNsYXNzPSJQbGFpblRleHQiPjxicj4NCjwv ZGl2Pg0KPGRpdiBjbGFzcz0iUGxhaW5UZXh0Ij5DaHJpc3RlcjwvZGl2Pg0KPGRpdiBjbGFzcz0i UGxhaW5UZXh0Ij48YnI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IlBsYWluVGV4dCI+PC9kaXY+DQo8 L3NwYW4+PC9mb250PjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo= --_000_HE1PR07MB3161966302E5C1AB1901874E93A10HE1PR07MB3161eurp_-- From nobody Mon Aug 26 12:06:30 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A1A18120C9C; Mon, 26 Aug 2019 12:06:21 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: curdle@ietf.org Message-ID: <156684638157.30541.17363240633687044451@ietfa.amsl.com> Date: Mon, 26 Aug 2019 12:06:21 -0700 Archived-At: Subject: [Curdle] I-D Action: draft-ietf-curdle-ssh-curves-10.txt X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 19:06:22 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CURves, Deprecating and a Little more Encryption WG of the IETF. Title : Secure Shell (SSH) Key Exchange Method using Curve25519 and Curve448 Authors : Aris Adamantiadis Simon Josefsson Mark D. Baushke Filename : draft-ietf-curdle-ssh-curves-10.txt Pages : 7 Date : 2019-08-26 Abstract: This document describes the conventions for using Curve25519 and Curve448 key exchange methods in the Secure Shell (SSH) protocol. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-curdle-ssh-curves-10 https://datatracker.ietf.org/doc/html/draft-ietf-curdle-ssh-curves-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-curdle-ssh-curves-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Aug 26 12:08:32 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07279120CA6; Mon, 26 Aug 2019 12:08:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net 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 4y9WoQyYw2w4; Mon, 26 Aug 2019 12:08:28 -0700 (PDT) Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8B05120C77; Mon, 26 Aug 2019 12:08:27 -0700 (PDT) Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x7QIrutT011135; Mon, 26 Aug 2019 12:08:24 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=to : cc : subject : in-reply-to : references : from : mime-version : content-type : content-id : date : message-id; s=PPS1017; bh=hHMAh/pQ3VFSr0gbUHzeMfdV/VcQQg6rOd/EUzVkeo8=; b=A0hDiotm7IHG3RAXmJSpdVipMnl/1Jn1fSCOsHFuAZWRd9nVwx6eLn95RgSx+IGxr98v SQv0HRdm3qlc91Yfah1SjIH39EiY+na92oyTZmsV7q43LzbhuCB409LffB2NfVITeqsr dSE4/tqewSQaoJ+bqnTMmYKO/4d2ByaNpFJf3a0vjx2u6TD6m/KjkgDdY1Ucx9nkOo2W kmCyBVqyI7jNZzD/vCnxqCwMoRVvZQRlIGaNJyOGFMBNOzXjKNsqqNiAeXYW/eFewt5z 1MteSoBRSIDngD+dOzMVc8dVxu62QgitP6iMsReFLKSYuY9jwfastCj914ts2We1V4P6 aA== Received: from nam01-bn3-obe.outbound.protection.outlook.com (mail-bn3nam01lp2057.outbound.protection.outlook.com [104.47.33.57]) by mx0b-00273201.pphosted.com with ESMTP id 2uknp7a76w-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 26 Aug 2019 12:08:23 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=b671OiDDekTdY4JxGEC5Q+uJY96f2Tns7XT5SRhj4MtV9nkJZeiHhDzHq4rfXv4yi4pljeSXOO+XOios+IQJqLWKvNMirc6X3cWO4aXJcDgJa83Z7E1lZfj/t3KhJM58jgJ94kRPmruQuYM/mSbeNoDfJTjtWgDJZzEDPIXcBUIjJ7mGluT2clhYkFd8Bv9nO5KGP1I2OfGiXEWTbsow37pnhu3dFjyayP/fuynbWp8cisE/dBE2/f4/NtukJsiSQ/bLZVH4wBH3MIwPJvvObhVHF34M9puQdR/ZWWfgKvW+1CydUaIcrCQFubNf4q/lxW1LTdCqD0n7vq1h2BWSCQ== 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=hHMAh/pQ3VFSr0gbUHzeMfdV/VcQQg6rOd/EUzVkeo8=; b=DKErWgXXdbsQcTDXIkrY6zxgq/zvCUnEbXGh3knjmsMVPRGmAoiF15nt+5/D4k8K4c2raHkdK3x/hW/yd/vkCWeQCYzaWwPn7loEgnwOlELJunyQMBIh72tP1xVnIw3R1YKHPzypUtqwR2Kovw5gdGSejN0HpEsJ3o7npa1yhYvOwpexXhHszWJ6OgDcWtDtDP//G1Xu+5iZjlROC6hy/KpdbJkaqJCMaMRHDVN9NkO8OGoi9/bxcPxHlYUsRguazt0ub/RfPO98dbuV4Ih96/k9l9bn92UVcI1RTbDzZzwdgcA7CTEHnyK4muRA/uhb6tFZul6uXTbZkoQRu/IACA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=softfail (sender ip is 66.129.239.12) smtp.rcpttodomain=ietf.org smtp.mailfrom=juniper.net; dmarc=fail (p=reject sp=reject pct=100) action=oreject header.from=juniper.net; dkim=none (message not signed); arc=none Received: from BYAPR05CA0003.namprd05.prod.outlook.com (2603:10b6:a03:c0::16) by DM6PR05MB5145.namprd05.prod.outlook.com (2603:10b6:5:7e::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.12; Mon, 26 Aug 2019 19:08:22 +0000 Received: from BY2NAM05FT006.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::204) by BYAPR05CA0003.outlook.office365.com (2603:10b6:a03:c0::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2220.9 via Frontend Transport; Mon, 26 Aug 2019 19:08:21 +0000 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender) Received: from P-EXFEND-EQX-01.jnpr.net (66.129.239.12) by BY2NAM05FT006.mail.protection.outlook.com (10.152.100.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2220.7 via Frontend Transport; Mon, 26 Aug 2019 19:08:21 +0000 Received: from P-EXBEND-EQX-02.jnpr.net (10.104.8.53) by P-EXFEND-EQX-01.jnpr.net (10.104.8.54) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 26 Aug 2019 12:08:20 -0700 Received: from p-mailhub01.juniper.net (10.104.20.6) by P-EXBEND-EQX-02.jnpr.net (10.104.8.53) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Mon, 26 Aug 2019 12:08:20 -0700 Received: from contrail-ubm16-mdb.svec1.juniper.net ([10.163.18.199]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id x7QJ8JG7028424; Mon, 26 Aug 2019 12:08:19 -0700 (envelope-from mdb@juniper.net) To: Christer Holmberg CC: "gen-art@ietf.org" , "curdle@ietf.org" , "ietf@ietf.org" , "draft-ietf-curdle-ssh-curves.all@ietf.org" In-Reply-To: References: <156647523885.14827.16394888562228822662@ietfa.amsl.com>, <19556.1566836922@contrail-ubm16-mdb.svec1.juniper.net> , <22345.1566843796@contrail-ubm16-mdb.svec1.juniper.net> Comments: In-reply-to: Christer Holmberg message dated "Mon, 26 Aug 2019 18:34:06 -0000." From: "Mark D. Baushke" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <23198.1566846499.1@contrail-ubm16-mdb.svec1.juniper.net> Date: Mon, 26 Aug 2019 12:08:19 -0700 Message-ID: <23199.1566846499@contrail-ubm16-mdb.svec1.juniper.net> X-EXCLAIMER-MD-CONFIG: e3cb0ff2-54e7-4646-8a04-0dae4ac7b136 X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-HT: Tenant X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(4636009)(396003)(136003)(376002)(39860400002)(346002)(2980300002)(199004)(189003)(70206006)(6916009)(46406003)(486006)(966005)(47776003)(446003)(476003)(126002)(11346002)(426003)(76176011)(26005)(23726003)(8936002)(6306002)(7696005)(305945005)(97876018)(2906002)(356004)(8676002)(86362001)(81156014)(81166006)(229853002)(558084003)(478600001)(117636001)(316002)(70586007)(5660300002)(97756001)(53936002)(6246003)(54906003)(16586007)(4326008)(336012)(50466002)(186003)(62816006); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB5145; H:P-EXFEND-EQX-01.jnpr.net; FPR:; SPF:SoftFail; LANG:en; PTR:InfoDomainNonexistent; A:1; MX:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 734f0f8a-453c-4904-7f6c-08d72a58c2fa X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(4710121)(4711137)(1401327)(4618075)(2017052603328); SRVR:DM6PR05MB5145; X-MS-TrafficTypeDiagnostic: DM6PR05MB5145: X-MS-Exchange-PUrlCount: 1 X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:3276; X-Forefront-PRVS: 01415BB535 X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: jl0/FxCjX4Cb0JyQyhSbBMyeJAUUfPEWVqMSvtII2MNJ1rOPBefiMrl6w8NfNF3h+InvDD7P13Q2398DgJlerVybP4pjAMS0TDrAFGTrHBx1Jwgqi7KIcC0BjrRNT3adYloAnPzhVKnK4kav/4aMYLkIYyuG/MMcuYVIvFGu37z8D4+zlY+BY8QDHBREIz5Xw6W0Z7uyFQzKzG5DBuP88bvjmg5xaPAvnY9ENpFgqgSyDeetvKUq8xQwGrQw1/gIrTNgR8FdcVUGd4QCdbpiGU3DvpLfDXlSFMYfG7BevJtdHE8JpvDXIR6wljK185MTuup0LcnQwlH1Tely6xz78xRIIRvDNTjwjqivObJuw3tv4f1F3MJX5Py0PitFRzMPaTPCfIxcQyhtClk/jpRVcmGCP1OUhrbKpSYLJ2q0E5M= X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 26 Aug 2019 19:08:21.2459 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 734f0f8a-453c-4904-7f6c-08d72a58c2fa X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12]; Helo=[P-EXFEND-EQX-01.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB5145 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-26_08:2019-08-26,2019-08-26 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 malwarescore=0 mlxscore=0 suspectscore=0 adultscore=0 impostorscore=0 lowpriorityscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxlogscore=593 priorityscore=1501 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908260179 Archived-At: Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 19:08:30 -0000 I have uploaded draft-ietf-curdle-ssh-curves-10.xml https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ with all of your suggested changes. This version addresses all of the review comments I have received to date. -- Mark From nobody Mon Aug 26 15:07:15 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 161EF12001A; Mon, 26 Aug 2019 15:07:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 VefVYMOXUVnO; Mon, 26 Aug 2019 15:07:12 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23234120013; Mon, 26 Aug 2019 15:07:11 -0700 (PDT) Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x7QM77w2006724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 26 Aug 2019 18:07:10 -0400 Date: Mon, 26 Aug 2019 17:07:07 -0500 From: Benjamin Kaduk To: "Mark D. Baushke" Cc: "curdle@ietf.org" , "draft-ietf-curdle-ssh-curves.all@ietf.org" Message-ID: <20190826220706.GS84368@kduck.mit.edu> References: <156647523885.14827.16394888562228822662@ietfa.amsl.com> <19556.1566836922@contrail-ubm16-mdb.svec1.juniper.net> <22345.1566843796@contrail-ubm16-mdb.svec1.juniper.net> <23199.1566846499@contrail-ubm16-mdb.svec1.juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <23199.1566846499@contrail-ubm16-mdb.svec1.juniper.net> User-Agent: Mutt/1.10.1 (2018-07-13) Archived-At: Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2019 22:07:14 -0000 Hi Mark, On Mon, Aug 26, 2019 at 12:08:19PM -0700, Mark D. Baushke wrote: > I have uploaded draft-ietf-curdle-ssh-curves-10.xml > > https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ > > with all of your suggested changes. > > This version addresses all of the review comments I have received to > date. Thanks! I've gone ahead and issued the IESG ballot, and expect this document to be assigned to the 2019-09-05 telechat agenda. -Ben From nobody Tue Aug 27 22:18:55 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DACD120823; Tue, 27 Aug 2019 22:18:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com 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 lm3DeTXYGTXR; Tue, 27 Aug 2019 22:18:51 -0700 (PDT) Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60043.outbound.protection.outlook.com [40.107.6.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B103112081D; Tue, 27 Aug 2019 22:18:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iSMeo5Ucgj/d2Ibf492SYg+MLQn9Bk05PiVPYCbDbskO5fu/cPdOD0e8belA7kz+2AcjGOaarJ9GifTcNERgwvBGtXTFzKEL4NVOoy6lGm2Dyue87xe5uO4iQOoxJlnTS1K+9ZdrI4cGTDn1NlHIfbOaKuSOKIEJUUtn9IjJ17cq/xUcS+XX2bNAnh3poivppxq6bcikWSLROit9gOC21oWKwwhvThAgR6DDIJoVUIbAD1+SSPmeKTrL9ZH1PTSfTPSqmXtauzZcEpF7gh9lmmV2gq3WHn7Ei6zMtM6o4o2/hu1NHCJQup4/guGkTfwIE0aaVWdp1D9/oYheXzq+vw== 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=svjdzke8O1+nBhjsXM+8S5kLewacQVKcWn/VARt+PmU=; b=nhbxuFmShTgZ+kIjlP06RJBPifPbUeVl52Jtq/1w5adSj9CMTljaj1+tCMwV9Ltye2+FYEH82bgoBtrEK6cP5JeCYi9Y8jTXfCdjkPN/wzV5Uh8wf/mHKrjfoz0H4bxa2bF9kHHwZhppTPkrbRtDp8Ox06McoQZwod/YEmR51fMjHRTcTQBQvkdhNrvjymWj+iZ+dQvnpODzuuams5GatBidLMJQT+NUrShjdv/ku5XgzMtby5sxUU+0OQzIvDa0+MHPbMqqB6Lz/4Z173dHVLz6sae2tbThQK38Fk8NH3XESKqX223iFojx8JBoBEqqJenDYdfF62DSRsKkpNXmBA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=svjdzke8O1+nBhjsXM+8S5kLewacQVKcWn/VARt+PmU=; b=dV0ukSg0HFQWVDiQUzc95sXtBuzHuKsrSsodrWOu4Wq031sI34z8VC72XRHpKdR0K52c+By6gjrQ6ePAiKdYB2m6inCM7fspSbHHGqp7qZLfGo3YM9sEfgs17pJsNgU/HCeZAaDJ93So070qqRL1UsORMBwI0iYlBbQ7UNOuLRs= Received: from HE1PR07MB3161.eurprd07.prod.outlook.com (10.170.245.23) by HE1PR07MB3146.eurprd07.prod.outlook.com (10.170.245.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2199.12; Wed, 28 Aug 2019 05:18:43 +0000 Received: from HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::f0a1:2199:7816:ff8d]) by HE1PR07MB3161.eurprd07.prod.outlook.com ([fe80::f0a1:2199:7816:ff8d%6]) with mapi id 15.20.2220.013; Wed, 28 Aug 2019 05:18:43 +0000 From: Christer Holmberg To: "Mark D. Baushke" CC: "gen-art@ietf.org" , "curdle@ietf.org" , "ietf@ietf.org" , "draft-ietf-curdle-ssh-curves.all@ietf.org" Thread-Topic: Genart last call review of draft-ietf-curdle-ssh-curves-09 Thread-Index: AQHVXCtcvr2YSg9UakaoGGnxJPuFPKcNqHWsgAAV3ACAAADEbYAAC9KAgAI83KA= Date: Wed, 28 Aug 2019 05:18:43 +0000 Message-ID: References: <156647523885.14827.16394888562228822662@ietfa.amsl.com>, <19556.1566836922@contrail-ubm16-mdb.svec1.juniper.net> , <22345.1566843796@contrail-ubm16-mdb.svec1.juniper.net> <23199.1566846499@contrail-ubm16-mdb.svec1.juniper.net> In-Reply-To: <23199.1566846499@contrail-ubm16-mdb.svec1.juniper.net> Accept-Language: en-US Content-Language: fi-FI X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; x-originating-ip: [37.136.1.66] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 9fb1fef7-39ff-42ba-7458-08d72b7731ff x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:HE1PR07MB3146; x-ms-traffictypediagnostic: HE1PR07MB3146: x-ms-exchange-purlcount: 1 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:4125; x-forefront-prvs: 014304E855 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(366004)(136003)(346002)(396003)(39860400002)(199004)(189003)(2906002)(71190400001)(256004)(71200400001)(66946007)(66556008)(66476007)(86362001)(14454004)(966005)(66066001)(3846002)(64756008)(74316002)(66446008)(76116006)(4744005)(6306002)(9686003)(4326008)(26005)(53936002)(25786009)(478600001)(6506007)(99286004)(33656002)(55016002)(6916009)(446003)(52536014)(6436002)(11346002)(54906003)(81156014)(5660300002)(76176011)(102836004)(476003)(8936002)(486006)(44832011)(316002)(8676002)(1941001)(7696005)(81166006)(6116002)(7736002)(305945005)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR07MB3146; H:HE1PR07MB3161.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: nilK+cG0PgqWKfAU9MTqV2bRE+OgTg3W/nBT0r9oOMEKrtm5gJAEhWzVMuMqgMut0YV0rtiHxMOOif0s+gfdIunuD/M6aNU1E4Tdqr5AQpqTuurLXcVoZTJ1AANUdNxf5ogijHAT6jP/7XnhymJ7r0n0WzlH0PGYgc2AagCfjYrCeQq9NOBaR8Sb9u767d+WkJZ85rKusvQdkuclZXMnitIkY1xtP6DoAcZF5o1YvsdIXJXCxJkYeTQEGIYCuiTW64PkqHf0o+hs8mQILt/+P2+4d09w5HFPNfDbuOTPlvy+SwXLtW6Yd1VoJc1Axq57jNXtOVfX5zoLKagCfiy+toX11xmlcV3gC998ed2QkScqh9C/PRVaadEG5tUyh2yCxesXMCxUnveoBl9iWUecGk+nFFDWwfvyaq3VsKLr9RI= x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-Network-Message-Id: 9fb1fef7-39ff-42ba-7458-08d72b7731ff X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Aug 2019 05:18:43.3283 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: 0KtBkF92lxeg54k41PxutSlYrqNUTwipePovO/uovIclVVOpofQt4/Co66pN5M1+IBb4gUfb3VZN+5hFpWg93JPALb8Oh8z+D2AXNIkXGZs= X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3146 Archived-At: Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-ssh-curves-09 X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2019 05:18:53 -0000 Hi, My gen-art issues have been properly addressed. Thanks! Regards, Christer -----Alkuper=E4inen viesti----- L=E4hett=E4j=E4: Mark D. Baushke =20 L=E4hetetty: maanantai 26. elokuuta 2019 22.08 Vastaanottaja: Christer Holmberg Kopio: gen-art@ietf.org; curdle@ietf.org; ietf@ietf.org; draft-ietf-curdle-= ssh-curves.all@ietf.org Aihe: Re: Genart last call review of draft-ietf-curdle-ssh-curves-09 I have uploaded draft-ietf-curdle-ssh-curves-10.xml https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ with all of your suggested changes. This version addresses all of the review comments I have received to date. -- Mark From nobody Wed Aug 28 04:02:33 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33576120108; Wed, 28 Aug 2019 04:02:31 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= To: "The IESG" Cc: draft-ietf-curdle-ssh-curves@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migault@ericsson.com, curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= Message-ID: <156699015116.32300.11396032996637636651.idtracker@ietfa.amsl.com> Date: Wed, 28 Aug 2019 04:02:31 -0700 Archived-At: Subject: [Curdle] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-curdle-ssh-curves-10=3A_=28with_DISCUSS_and_COMMENT=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2019 11:02:31 -0000 Mirja Kühlewind has entered the following ballot position for draft-ietf-curdle-ssh-curves-10: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Question to the IESG/responsible AD: I found this: "Appendix A. Copying conditions Regarding this entire document or any portion of it, the authors make no guarantees and are not responsible for any damage resulting from its use. The authors grant irrevocable permission to anyone to use, modify, and distribute it in any way that does not diminish the rights of anyone else to use, modify, and distribute it, provided that redistributed derivative works do not contain misleading author or version information. Derivative works need not be licensed under similar terms." Does it make sense to have this in addition to the usual IETF terms? And/or why is this needed here? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- One minor comment: In section 3, would it make sense to actually name what the "appropriate SSH "protocol error"" is? From nobody Wed Aug 28 04:47:17 2019 Return-Path: X-Original-To: curdle@ietf.org Delivered-To: curdle@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 636F612004A; Wed, 28 Aug 2019 04:47:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Alexey Melnikov via Datatracker To: "The IESG" Cc: draft-ietf-curdle-ssh-curves@ietf.org, Daniel Migault , curdle-chairs@ietf.org, daniel.migault@ericsson.com, curdle@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.100.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Alexey Melnikov Message-ID: <156699282735.32507.5324360458291266660.idtracker@ietfa.amsl.com> Date: Wed, 28 Aug 2019 04:47:07 -0700 Archived-At: Subject: [Curdle] Alexey Melnikov's No Objection on draft-ietf-curdle-ssh-curves-10: (with COMMENT) X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2019 11:47:08 -0000 Alexey Melnikov has entered the following ballot position for draft-ietf-curdle-ssh-curves-10: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-curves/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The following text in Section 1: At the time of writing this specification, high-quality free implementations of Curve25519 has been in deployed use for several years, while Curve448 implementations are slowly appearing, so it is accepted that adoption of Curve448 would be slower. would not age well once the RFC is published. I suggest this is moved from the draft to the shepherding write-up. Also, SHA-256 and SHA-512 need to be normative references. From nobody Wed Aug 28 08:54:15 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E69B112088A; Wed, 28 Aug 2019 08:53:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net 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 TV-iYS2cH1aV; Wed, 28 Aug 2019 08:53:47 -0700 (PDT) Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 403A7120828; Wed, 28 Aug 2019 08:53:47 -0700 (PDT) Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x7SFoQm7011412; Wed, 28 Aug 2019 08:53:40 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=to : cc : subject : in-reply-to : references : from : mime-version : content-type : date : message-id; s=PPS1017; bh=xSKtnQY1RdaKnwX+PK+ZTBoKxxG+RshMrncjzeDkP3k=; b=XWMmj7w9hH3ccYjg5segBogWDtSziYJV2hwjrLcdPsDwkaBEyq2PXIHm+yHt07MVB+D/ gqPNFbIkXx7D9dqGVgZ5OyxR9iNYICfdX1rfCPc6XLNcRopTGhc4IndJDITpKh1v+i3K mWAyl2kCWOOYSaYKGeB9MGytPCJK18ZoSU7mmBdeO88blTxxsremrjSuqpK5T4pHTwPU +P4T0R09gdOs45poHepPJeq16RGspBjEfoyg1HgHTOjZo54Jnpoq2YM5Au/ZRfs44hTP axR4PbAB+o2swNegi7rvFL45142baYLvZq8KwByUGBaTH9o0NcFGy+NJ9RhIl1p020Zy Tw== Received: from nam01-by2-obe.outbound.protection.outlook.com (mail-by2nam01lp2051.outbound.protection.outlook.com [104.47.34.51]) by mx0b-00273201.pphosted.com with ESMTP id 2unhwgh1hx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 28 Aug 2019 08:53:40 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LGCWYxMymJmq50ahEzgzA4hUQaVpjDTUFJIOpnLnt7ya8wAAIoYWMw7WwSMB+NlP9wVHvD8WY3aXgdj2sWhop6PAh53C8BkOztxShUmRF1vF+0+kh0a+dH+mw0Bfnu0YNANfD2iBy4WM5bFmc9P72IQZuWHwltt7Nyg/LII9E0hrTcaMVaR17izHfUeg3hnyzeP26drYuGjNxshZ9fNNNMPoPSC76lI6buzEeRgLuoO1vCXmVW5N0Og4E6TaNH2uoda0KPF+dfhFXNOAkEswo3Qx8u+XcF9NuGCb5TYPU2ZFcTvsMM6fyCuzJZeeJJa63gjvkhz0tnrBGLEvJFnuhg== 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=xSKtnQY1RdaKnwX+PK+ZTBoKxxG+RshMrncjzeDkP3k=; b=iapXWox9nsR0floz4c6fKz9zIsec7paICBPKlwzcU7zq+jpozaZrYvSyA55yhiBPZgNloLcEAECCz/p/W9rDGGd07m8mV34TwFKaycKMEhZf1MBFVxqrnbTqs1NsFjpB8NdNrzZhfECTOkyu3OQqZhyXPu+TuYJ3jI1ROopvM3jpHZVq/XIn0sEid7DQGEGyiAEOeGVcz57eh2v3GZuW7/qo5AIiNiA2MwZ9sAh6Sgr1+7iVkENqkUvW/QJa9u9+6ikUKpaxvydGnvC3k6e4aRqoGP3fnX8op0uoBQlxSQ+g1BnOxrIcseEsseJw05+0tgK8IN7xkHWbrzvZJOIBHg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=softfail (sender ip is 66.129.239.12) smtp.rcpttodomain=ietf.org smtp.mailfrom=juniper.net; dmarc=fail (p=reject sp=reject pct=100) action=oreject header.from=juniper.net; dkim=none (message not signed); arc=none Received: from CH2PR05CA0020.namprd05.prod.outlook.com (2603:10b6:610::33) by BN6PR05MB3604.namprd05.prod.outlook.com (2603:10b6:405:3e::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2220.14; Wed, 28 Aug 2019 15:53:26 +0000 Received: from CO1NAM05FT032.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::207) by CH2PR05CA0020.outlook.office365.com (2603:10b6:610::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2199.14 via Frontend Transport; Wed, 28 Aug 2019 15:53:25 +0000 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.12 as permitted sender) Received: from P-EXFEND-EQX-01.jnpr.net (66.129.239.12) by CO1NAM05FT032.mail.protection.outlook.com (10.152.96.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.2220.7 via Frontend Transport; Wed, 28 Aug 2019 15:53:25 +0000 Received: from P-EXBEND-EQX-01.jnpr.net (10.104.8.52) by P-EXFEND-EQX-01.jnpr.net (10.104.8.54) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 28 Aug 2019 08:53:24 -0700 Received: from p-mailhub01.juniper.net (10.104.20.6) by P-EXBEND-EQX-01.jnpr.net (10.104.8.52) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Wed, 28 Aug 2019 08:53:24 -0700 Received: from contrail-ubm16-mdb.svec1.juniper.net ([10.163.18.199]) by p-mailhub01.juniper.net (8.14.4/8.11.3) with ESMTP id x7SFrNIW028831; Wed, 28 Aug 2019 08:53:23 -0700 (envelope-from mdb@juniper.net) To: =?us-ascii?Q?=3D=3Futf-8=3Fq=3FMirja=5FK=3DC3=3DBChlewind=3F=3D?= CC: The IESG , , Daniel Migault , , In-Reply-To: <156699015116.32300.11396032996637636651.idtracker@ietfa.amsl.com> References: <156699015116.32300.11396032996637636651.idtracker@ietfa.amsl.com> Comments: In-reply-to: =?us-ascii?Q?=3D=3Futf-8=3Fq=3FMirja=5FK=3DC3=3DBCh?= =?us-ascii?Q?lewind=5Fvia=5FDatatracker=3F=3D?= message dated "Wed, 28 Aug 2019 04:02:31 -0700." From: "Mark D. Baushke" X-Phone: +1 408 745-2952 (Office) X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1 X-Face: #8D_6URD2G%vC.hzU X-EXCLAIMER-MD-CONFIG: e3cb0ff2-54e7-4646-8a04-0dae4ac7b136 X-EOPAttributedMessage: 0 X-MS-Office365-Filtering-HT: Tenant X-Forefront-Antispam-Report: CIP:66.129.239.12; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(4636009)(39860400002)(346002)(136003)(396003)(376002)(2980300002)(189003)(199004)(26005)(476003)(97876018)(5660300002)(6916009)(356004)(446003)(47776003)(316002)(186003)(2906002)(229853002)(117636001)(50466002)(7696005)(86362001)(50226002)(51416003)(76176011)(4326008)(4744005)(336012)(54906003)(16586007)(426003)(305945005)(81156014)(81166006)(224303003)(70586007)(478600001)(11346002)(6246003)(126002)(70206006)(486006)(53936002)(8936002)(48376002)(62816006); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR05MB3604; H:P-EXFEND-EQX-01.jnpr.net; FPR:; SPF:SoftFail; LANG:en; PTR:InfoDomainNonexistent; MX:1; A:1; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: a0e07c8d-852b-4ecf-5e65-08d72bcfdcbd X-Microsoft-Antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(4710121)(4711137)(1401327)(4618075)(2017052603328); SRVR:BN6PR05MB3604; X-MS-TrafficTypeDiagnostic: BN6PR05MB3604: X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:10000; X-Forefront-PRVS: 014304E855 X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Message-Info: Nhk48jIRKvLJ7h3YTE3wD/Ogu3tsZ0aKFnZZTuriHXxoK00s9+FOpd9Hi9OFiT8Gi3iCwwffOdJ/qiEbemsY+ST7UNP4M9JWFSazkuV2Bzu8cEgh55ZuMShKjqCl/O9sGRP2hlgFaFS4WbyxR2By2YRL8/dooG6WxizQghRKqtU8LGOo1i6HEBUIx085CBhJ89R6QBd2YpcircAMimb8fiQQ91HLlNc6BdD9ijb0KPeud1wC87c92ThsVAd7it6vWUjwUm+dTntCU7Dw1Mz8jCnp3Nxtqjs8tdFMvOjp3YBRU1C7yHAmjUo1pYvdW+UX1632ysFxX3H5nrUV9B+jHI0fZ7y0POeLwEfuPZ5mDNCtf/8Kg2OfJqeQSxmAoic8p1WH7RaY0QErfaEd0/mITXewqUYv7IwO2ouZ6k6wDj0= X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 28 Aug 2019 15:53:25.5205 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: a0e07c8d-852b-4ecf-5e65-08d72bcfdcbd X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.12]; Helo=[P-EXFEND-EQX-01.jnpr.net] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB3604 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.70,1.0.8 definitions=2019-08-28_08:2019-08-28,2019-08-28 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 clxscore=1011 bulkscore=0 phishscore=0 malwarescore=0 mlxlogscore=545 suspectscore=0 impostorscore=0 lowpriorityscore=0 adultscore=0 priorityscore=1501 mlxscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908280160 Archived-At: Subject: Re: [Curdle] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-curdle-ssh-curves-10=3A_=28with_DISCUSS_and_COMMENT=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2019 15:53:53 -0000 Hi Marja, I did not write the original "Copying Conditions" section and would rather have the approval of the other authors before it is removed. I have no objections myself. In section 3, the appropriate SSH "protocol error" might be one of a two: SSH_ERR_KEY_INVALID_EC_VALUE for zeros found for the all-zero shared secret and SSH_ERR_SIGNATURE_INVALID if the blob is not the correct size for a public key However, an implementation miight return SSH_ERR_SIGNATURE_INVALID rather than SSH_ERR_KEY_INVALID_EC_VALUE depending on how the implementation was written. As long as the connection aborts and does not continue in the case of a "protocol error", it is sufficient in my opinion. Is it really needful to be prescriptive in this given that many implementations of this code have already been fielded and I do not have any ability to know which design choices they made? -- Mark From nobody Wed Aug 28 10:08:27 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B79E7120143; Wed, 28 Aug 2019 10:08:25 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 IOprfeE3mnln; Wed, 28 Aug 2019 10:08:24 -0700 (PDT) Received: from korell.badcode.be (korell.badcode.be [213.167.241.246]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0797D1200B2; Wed, 28 Aug 2019 10:08:23 -0700 (PDT) Received: from [192.168.128.199] (host-85-201-47-162.dynamic.voo.be [85.201.47.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by korell.badcode.be (Postfix) with ESMTPSA id C051B9E0AB; Wed, 28 Aug 2019 19:03:30 +0200 (CEST) To: "Mark D. Baushke" , =?UTF-8?Q?Mirja_K=c3=bchlewind?= Cc: The IESG , draft-ietf-curdle-ssh-curves@ietf.org, Daniel Migault , curdle-chairs@ietf.org, curdle@ietf.org References: <156699015116.32300.11396032996637636651.idtracker@ietfa.amsl.com> <18058.1567007603@contrail-ubm16-mdb.svec1.juniper.net> From: Aris Adamantiadis Message-ID: Date: Wed, 28 Aug 2019 19:08:21 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <18058.1567007603@contrail-ubm16-mdb.svec1.juniper.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [Curdle] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-curdle-ssh-curves-10=3A_=28with_DISCUSS_and_COMMENT=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2019 17:08:26 -0000 Le 28-08-19 à 17:53, Mark D. Baushke a écrit : > In section 3, the appropriate SSH "protocol error" might be one of a > two: > > SSH_ERR_KEY_INVALID_EC_VALUE for zeros found for the all-zero shared > secret > > and > > SSH_ERR_SIGNATURE_INVALID if the blob is not the correct size for a > public key > > However, an implementation miight return SSH_ERR_SIGNATURE_INVALID > rather than SSH_ERR_KEY_INVALID_EC_VALUE depending on how the > implementation was written. > > As long as the connection aborts and does not continue in the case of a > "protocol error", it is sufficient in my opinion. > > Is it really needful to be prescriptive in this given that many > implementations of this code have already been fielded and I do not > have any ability to know which design choices they made? Hi Mark, I would think it's best that as little information as possible about the error is sent over the SSH connection. This vector was historically used to exploit other cryptographic protocols, enabling attacks such as padding oracles and others. Additionally it doesn't really help the end user who would see this message, because this is clearly an implementation issue within the SSH software stack, not something that the user can tweak in a configuration file. I'd then recommend a SHOULD send SSH_ERR_SIGNATURE_INVALID for all cases where protocol errors happen when handling the shared secret or the peer's key, if we really wish to be prescriptive, something I don't think is important. From nobody Wed Aug 28 15:37:25 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03CDF1200E3 for ; Wed, 28 Aug 2019 15:37:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=timeheart.net 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 bwSXb4fDn8Et for ; Wed, 28 Aug 2019 15:37:20 -0700 (PDT) Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D6BB12024E for ; Wed, 28 Aug 2019 15:37:20 -0700 (PDT) Received: by mail-pl1-x631.google.com with SMTP id w11so620971plp.5 for ; Wed, 28 Aug 2019 15:37:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timeheart.net; s=mail; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=B7sQUH35b5LgNZlQ9qOGfmyqYi5h7gTlv7KWhHybh78=; b=KS2UbWI56+0SD+yfWhyJfgZWQ830wTqSwg1gYXg8FewoM3bMTm2zJeGIpNjqtEu0FT 2t7byqHIwOhshUI6rXI36ls4WxfAT7k0Dshb4iF8ejWK/XKRG5sMM2/0joaUM/7gBMWv etxIQXKOwK9dR4c/x38OFgOWDhkpao4Ltcbcs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=B7sQUH35b5LgNZlQ9qOGfmyqYi5h7gTlv7KWhHybh78=; b=g/+VXYQp7JG7Q7gWrkGHwyom511dW1diyErygRZxwraz4pcZ/+whFlIFD7mapcoGrA HjewllE0QeJj1yQyQnkhoD7fZz5WORCOlKLnK41fE+3JwVpDkOLLe0gizMjfwzRcitUs Y3Xf/9cu3wksGXHkhO6BCVCuCqoncykSfW0zvrBIlTWQ/iCjxR4a4oDzJws+8bVjW1YD 82hS4iVVh2A4hFaTypI8dejCIBGJNRD93W0Kdka9c7+oLNo0v4TDFsXSp4+7WQ/K4zjv nnSzs24NV3p+PsuLNKJK9basKPy5AhPSqcFn8rDxWojViGYCCZ/LKIzLvY6FWiJYz24y HP6Q== X-Gm-Message-State: APjAAAUC1uU4VEaIhHeSm5JHQdY57jn10zX4rb1qMslcBzVBdAVtr69N QrVKGLB8EWTX0OYcIXFco8pijg== X-Google-Smtp-Source: APXvYqytc6mEWdENSnZeF9Y5L/ejg6ofni62p8p7Cml4o61vvEiBJ8VHsF7a/g1/mGiWJl8tV3kqSA== X-Received: by 2002:a17:902:7886:: with SMTP id q6mr6818836pll.78.1567031839865; Wed, 28 Aug 2019 15:37:19 -0700 (PDT) Received: from [10.17.102.191] ([155.64.23.53]) by smtp.gmail.com with ESMTPSA id o4sm202234pje.28.2019.08.28.15.37.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Aug 2019 15:37:19 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Ron Frederick In-Reply-To: Date: Wed, 28 Aug 2019 15:37:17 -0700 Cc: "Mark D. Baushke" , =?utf-8?Q?Mirja_K=C3=BChlewind?= , curdle@ietf.org, Daniel Migault , draft-ietf-curdle-ssh-curves@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <6A321C2C-7EE8-4290-888A-7AF19863BEA0@timeheart.net> References: <156699015116.32300.11396032996637636651.idtracker@ietfa.amsl.com> <18058.1567007603@contrail-ubm16-mdb.svec1.juniper.net> To: Aris Adamantiadis X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [Curdle] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-curdle-ssh-curves-10=3A_=28with_DISCUSS_and_COMMENT=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2019 22:37:24 -0000 On Aug 28, 2019, at 10:08 AM, Aris Adamantiadis wrote: > Le 28-08-19 =C3=A0 17:53, Mark D. Baushke a =C3=A9crit : >> In section 3, the appropriate SSH "protocol error" might be one of a >> two: >>=20 >> SSH_ERR_KEY_INVALID_EC_VALUE for zeros found for the all-zero = shared >> secret >>=20 >> and >> SSH_ERR_SIGNATURE_INVALID if the blob is not the correct size = for a >> public key >>=20 >> However, an implementation miight return SSH_ERR_SIGNATURE_INVALID >> rather than SSH_ERR_KEY_INVALID_EC_VALUE depending on how the >> implementation was written. >>=20 >> As long as the connection aborts and does not continue in the case of = a >> "protocol error", it is sufficient in my opinion. >>=20 >> Is it really needful to be prescriptive in this given that many >> implementations of this code have already been fielded and I do not >> have any ability to know which design choices they made? >=20 > Hi Mark, >=20 > I would think it's best that as little information as possible about = the error is sent over the SSH connection. This vector was historically = used to exploit other cryptographic protocols, enabling attacks such as = padding oracles and others. Additionally it doesn't really help the end = user who would see this message, because this is clearly an = implementation issue within the SSH software stack, not something that = the user can tweak in a configuration file. >=20 > I'd then recommend a SHOULD send SSH_ERR_SIGNATURE_INVALID for all = cases where protocol errors happen when handling the shared secret or = the peer's key, if we really wish to be prescriptive, something I don't = think is important. The SSH_ERR_* names are not actually wire protocol constructs, so I = don=E2=80=99t believe they should be used in this spec. =46rom what I = can see, they are values defined internally by OpenSSH and LibSSH (and = possibly others), but in the end they are converted to a text string = before being used anywhere. I didn=E2=80=99t track all the way through = the code to see if the text strings ever appear on the wire or not or = only in local log messages, but if they did appear on the wire I expect = they would be as the =E2=80=9Cdescription=E2=80=9D text in an = SSH_MSG_DISCONNECT message. The =E2=80=9Creason code=E2=80=9D in that = message comes from a much smaller list (defined in RFC 4253 section = 11.1) and would probably be set to SSH_DISCONNECT_PROTOCOL_ERROR or = perhaps SSH_DISCONNECT_KEY_EXCHANGE_FAILED. I agree that this spec should not attempt to go into detail about what = error is returned, especially not for a text string like this. I could = see potentially recommending that a disconnect be performed, but even = attempting to recommend the specific disconnect reason runs the risk of = not matching what existing implementations are currently doing in this = case and I see very little value in trying to standardize the exact = disconnect reason. --=20 Ron Frederick ronf@timeheart.net From nobody Wed Aug 28 15:46:47 2019 Return-Path: X-Original-To: curdle@ietfa.amsl.com Delivered-To: curdle@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 922061200E3; Wed, 28 Aug 2019 15:46:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 igDj8c7ZdR8d; Wed, 28 Aug 2019 15:46:33 -0700 (PDT) Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE6861200CD; Wed, 28 Aug 2019 15:46:33 -0700 (PDT) Received: by mail-ot1-x330.google.com with SMTP id o101so1468036ota.8; Wed, 28 Aug 2019 15:46:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uVnU3SjgVehWFFaJzesZUTpYZldW6sFzFAy64UyNPMg=; b=X7tYTA74Opv/3IFc+GML5l8Zswe6uwHfKrMz5+KrrBEnlTrCjibLyPh7yAjZ5aSmME iRdRtX68UAEIDpmgxMSLieRA/xu5iZgdtpOZtkg67V3VZASco2tArMnTbVsO8lFxUA5K l6Rr45KiWs+G7CzJ/CmHgeFA2JN5N+19dJJWLohBVOqrQ4awe2OZcA7u+mWPkuXgxsgY MbNaQHqM1fsKS6sfvPU4gTwEmn0xwKA/qWVYigjOoJHL6KGLAKTo/hqdQROY6fkNGuqS t6HMADoMz8Po3DIhi3WfwIQY4KOMZbejHiT13FUqb+YiDbDHkSAxWesRFYZ73u7H79ut IWWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uVnU3SjgVehWFFaJzesZUTpYZldW6sFzFAy64UyNPMg=; b=DdzMImrrAw0BmO6wA3GV1yqBe0Xfu87RrsBBj1Y2SxdIxZFH4AgFYLgV/gw1ESanuy LGH4QkiHo0ZJ7Gp3MpptJ8esTJwXq7BXrlKoW4OYUbaagFmADrrcHUROKlxKLz1Td29c xNTGXZnm9b8Wy1M7T+Zm76d+ZC0NOFp72rKfehsQC5xR5vIYsgjuD763YA17v3KinNrB 17JtBrkXdvq4hUtbRY+Eg59q2odO32N1DgBmmMuC530uG+wI71lnowQaKUQN8jYIqOxm zRqwkskLqdmkmlGDEy+bRhvZLh7Red2uUoNrx87gTxvfRGUlFdZGxiLwieFGU1sgfMOR qCBw== X-Gm-Message-State: APjAAAV4NZJykKYlM9ttHL6IjHdS+xD5q8tFMzfFUcRiOCQ5sBM6DNxe CaXl8olnVthiJa6AsPdJgLWFexz8qVQeoGSkoBc= X-Google-Smtp-Source: APXvYqzCPbIFeEBOKImWwlpteKNEJityOgzwW1JTqNxS5Rm4J5y0K5yBuRJiszz4+Ur+h3ssvWtgxzhD8DJjtBqGeiI= X-Received: by 2002:a9d:4004:: with SMTP id m4mr4858856ote.146.1567032393240; Wed, 28 Aug 2019 15:46:33 -0700 (PDT) MIME-Version: 1.0 References: <156699015116.32300.11396032996637636651.idtracker@ietfa.amsl.com> <18058.1567007603@contrail-ubm16-mdb.svec1.juniper.net> In-Reply-To: From: denis bider Date: Wed, 28 Aug 2019 17:46:21 -0500 Message-ID: To: Aris Adamantiadis Cc: "Mark D. Baushke" , =?UTF-8?Q?Mirja_K=C3=BChlewind?= , curdle , Daniel Migault , draft-ietf-curdle-ssh-curves@ietf.org, curdle-chairs , The IESG Content-Type: multipart/alternative; boundary="000000000000269b500591352991" Archived-At: Subject: Re: [Curdle] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-curdle-ssh-curves-10=3A_=28with_DISCUSS_and_COMMENT=29?= X-BeenThere: curdle@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "List for discussion of potential new security area wg." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2019 22:46:37 -0000 --000000000000269b500591352991 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable With regard to the following: > Additionally it doesn't really help the end user who would > see this message, because this is clearly an implementation > issue within the SSH software stack, not something that the > user can tweak in a configuration file. I think it's important to note that this reasoning, in general, is false. As someone who has directly supported users of SSH software over 20 years, it is highly useful if the user can send log files which contain technical information, even if the user doesn't understand that information. It can dramatically reduce the effort needed to figure out an issue, and increases the odds that it will be figured out at all. The part of the argument about protecting sensitive information is valid, but implementers also tend to run with that much further than it's useful. For example, there are implementations which use this reasoning to try to deny the other party information about the software name and version in the SSH version string. This greatly frustrates figuring out problems when connecting to those implementations (what software is this to begin with?) and makes it difficult to implement compatibility workarounds (how do we tell this broken implementation from others when it's going out of its way to disguise itself?). From this perspective, I am thankful to developers like OpenSSH for their policy to always include the software name and version in the SSH version string, that's a godsend that greatly helps when we need to work around a compatibility issue. In general - protect sensitive information, yes; but consider that every piece of information that's removed also makes things substantially more difficult for tech support and compatibility. denis On Wed, Aug 28, 2019 at 12:08 PM Aris Adamantiadis wrote: > Le 28-08-19 =C3=A0 17:53, Mark D. Baushke a =C3=A9crit : > > > In section 3, the appropriate SSH "protocol error" might be one of a > > two: > > > > SSH_ERR_KEY_INVALID_EC_VALUE for zeros found for the all-zero shared > > secret > > > > and > > > > SSH_ERR_SIGNATURE_INVALID if the blob is not the correct size for a > > public key > > > > However, an implementation miight return SSH_ERR_SIGNATURE_INVALID > > rather than SSH_ERR_KEY_INVALID_EC_VALUE depending on how the > > implementation was written. > > > > As long as the connection aborts and does not continue in the case of a > > "protocol error", it is sufficient in my opinion. > > > > Is it really needful to be prescriptive in this given that many > > implementations of this code have already been fielded and I do not > > have any ability to know which design choices they made? > > Hi Mark, > > I would think it's best that as little information as possible about the > error is sent over the SSH connection. This vector was historically used > to exploit other cryptographic protocols, enabling attacks such as > padding oracles and others. Additionally it doesn't really help the end > user who would see this message, because this is clearly an > implementation issue within the SSH software stack, not something that > the user can tweak in a configuration file. > > I'd then recommend a SHOULD send SSH_ERR_SIGNATURE_INVALID for all cases > where protocol errors happen when handling the shared secret or the > peer's key, if we really wish to be prescriptive, something I don't > think is important. > > > _______________________________________________ > Curdle mailing list > Curdle@ietf.org > https://www.ietf.org/mailman/listinfo/curdle > --000000000000269b500591352991 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
With regard to the following:

>= =C2=A0Additionally it doesn't really help the end user who would
> see this message, b= ecause this is clearly an implementation
> issue within the SSH software stack, not something that the
> user can tweak in a co= nfiguration file.

I think it's important to note that this reasoning, in general, is = false. As someone who has directly supported users of SSH software over 20 = years, it is highly useful if the user can send log files which contain tec= hnical information, even if the user doesn't understand that informatio= n. It can dramatically reduce the effort needed to figure out an issue, and= increases the odds that it will be figured out at all.

The part of the argument about protecting se= nsitive information is valid, but implementers also tend to run with that m= uch further than it's useful. For example, there are implementations wh= ich use this reasoning to try to deny the other party information about the= software name and version in the SSH version string. This greatly frustrat= es figuring out problems when connecting to those implementations (what sof= tware is this to begin with?) and makes it difficult to implement compatibi= lity workarounds (how do we tell this broken implementation from others whe= n it's going out of its way to disguise itself?). From this perspective= , I am thankful to developers like OpenSSH for their policy to always inclu= de the software name and version in the SSH version string, that's a go= dsend that greatly helps when we need to work around a compatibility issue.=

=
In general - protect sensitive information, yes; but consider th= at every piece of information that's removed also makes things substant= ially more difficult for tech support and compatibility.

denis


On Wed, Aug 28, 20= 19 at 12:08 PM Aris Adamantiadis <ari= s@badcode.be> wrote:
Le 28-08-19 =C3=A0 17= :53, Mark D. Baushke a =C3=A9crit=C2=A0:

> In section 3, the appropriate SSH "protocol error" might be = one of a
> two:
>
>=C2=A0 =C2=A0 SSH_ERR_KEY_INVALID_EC_VALUE for zeros found for the all-= zero shared
>=C2=A0 =C2=A0 secret
>
> and
>=C2=A0 =C2=A0
>=C2=A0 =C2=A0 SSH_ERR_SIGNATURE_INVALID if the blob is not the correct = size for a
>=C2=A0 =C2=A0 public key
>
> However, an implementation miight return SSH_ERR_SIGNATURE_INVALID
> rather than SSH_ERR_KEY_INVALID_EC_VALUE depending on how the
> implementation was written.
>
> As long as the connection aborts and does not continue in the case of = a
> "protocol error", it is sufficient in my opinion.
>
> Is it really needful to be prescriptive in this given that many
> implementations of this code have already been fielded and I do not > have any ability to know which design choices they made?

Hi Mark,

I would think it's best that as little information as possible about th= e
error is sent over the SSH connection. This vector was historically used to exploit other cryptographic protocols, enabling attacks such as
padding oracles and others. Additionally it doesn't really help the end=
user who would see this message, because this is clearly an
implementation issue within the SSH software stack, not something that
the user can tweak in a configuration file.

I'd then recommend a SHOULD send SSH_ERR_SIGNATURE_INVALID for all case= s
where protocol errors happen when handling the shared secret or the
peer's key, if we really wish to be prescriptive, something I don't=
think is important.


_______________________________________________
Curdle mailing list
Curdle@ietf.org https://www.ietf.org/mailman/listinfo/curdle
--000000000000269b500591352991--