IETF Logo Mail Archive

Re: [Curdle] draft-ietf-curdle-ssh-modp-dh-sha2

Yoav Nir <ynir.ietf@gmail.com> Tue, 28 March 2017 18:39 UTC

Return-Path: <ynir.ietf@gmail.com>
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 E75DA1297CC for <curdle@ietfa.amsl.com>; Tue, 28 Mar 2017 11:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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=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 SXfsCVSGMHOt for <curdle@ietfa.amsl.com>; Tue, 28 Mar 2017 11:39:38 -0700 (PDT)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 9B8E0124BFA for <curdle@ietf.org>; Tue, 28 Mar 2017 11:39:38 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id 190so29464785itm.0 for <curdle@ietf.org>; Tue, 28 Mar 2017 11:39:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Ev5YjHYsGWq6lWJEf9zoTMA1tIkbWrG3DtPAvCh3mBY=; b=jFSZoec3payejy0SG6k0PqTK9l7ZfjwhCbaRc64tr6Im5njFinUrOBXTKfsRvELsYH vGIXsVNHZYMmMBurqwQvv46ttPLPR6Lfa+Yb7Q6U0sUK3HJMmY0+ZPo+1o8yCSeh5YOv z8Cq4LVG8+fEQMSkwbQZu1lh7C8eCFwVcLDBKd1BzDg0/AeShvBp16PSDVLzsHbvHmwn PrHOO6+QOJYSyNq7hNoI84G0RRNWTgFekhtoZ+1wxoM+MRzqbEbWgpCx3PzS7og7qtEb bb0+YNMWfSn+c87PIO20ozRmY+SUm+z015oVniCVIppazTynhTdBbkqOqC1VXFJyNO7t pkJA==
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=Ev5YjHYsGWq6lWJEf9zoTMA1tIkbWrG3DtPAvCh3mBY=; b=Ji9EfgMF9GEa+UpQljIdR5cexZS4PaZ8MsOMdzJOrVIL9jIMeEeQpUi4nh23U9bniy zQDM9QAn3CKi5WsoJDtcESfYmdGlitl372usJ4uzhYMh2u7nCJPLkERuFGydQjNQrwdu 7n6LGPnUYtmTSWYiN+EzEBtoLhckUO1bIwLZsDM2dRwUBHF/KGmBhsk+eQmLohYS7gWW JQ/aAgFcH8o286GMdj/nWgDY2//Pt+u4ivjfRBgIKnBvWEQSlQIIQPhGEBZbTZYbK/oU tkaFCywqg522yUHl2HSlo1gB2tTb/RcRFj0qivrwwZWL/cM9qzDWkaXmoJN2wntvL6oG 3aUA==
X-Gm-Message-State: AFeK/H2VtvuCJhGsk6KTQCkK4HRgTDGLyTpz8AQ72cloJNnP3qhy38nu0JXQ0azHhYwHww==
X-Received: by 10.36.26.66 with SMTP id 63mr16370617iti.27.1490726377793; Tue, 28 Mar 2017 11:39:37 -0700 (PDT)
Received: from t2001067c03700128102957629935b2b3.v6.meeting.ietf.org (t2001067c03700128102957629935b2b3.v6.meeting.ietf.org. [2001:67c:370:128:1029:5762:9935:b2b3]) by smtp.gmail.com with ESMTPSA id y203sm2321974iod.11.2017.03.28.11.39.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Mar 2017 11:39:37 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <DA08F29C-A756-4AEE-8051-C93DE669B3B6@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_49D2FC09-DA35-4531-9540-81EB96FB9948"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 28 Mar 2017 13:39:35 -0500
In-Reply-To: <6ab576118c6945f4ba888dd403cf2471@usma1ex-dag1mb1.msg.corp.akamai.com>
Cc: "Mark D. Baushke" <mdb@juniper.net>, curdle <curdle@ietf.org>
To: Rich Salz <rsalz@akamai.com>
References: <CADZyTkmr0WF3BOBby3rObBGGQaqMUq=0Ssc7NB9PAgPFDrk7dA@mail.gmail.com> <30381.1490720068@eng-mail01.juniper.net> <6ab576118c6945f4ba888dd403cf2471@usma1ex-dag1mb1.msg.corp.akamai.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/_Z0ZipUCFX8pONVDCU7v2Z9LQLU>
Subject: Re: [Curdle] draft-ietf-curdle-ssh-modp-dh-sha2
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 18:39:41 -0000

+1

Using the IKE groups is fine. Using the TLS groups is fine. No need for new SSH groups generated in the same way.

(note that I said the same when DKG proposed generating new groups for TLS rather than use the IKE groups)

> On 28 Mar 2017, at 13:19, Salz, Rich <rsalz@akamai.com> wrote:
> 
> I think the in-room consensus was that since this is deployed and used in IKE, it's okay and that no work is needed.
> 
> 
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle

v2.23.0 | Report a Bug | By Email