Re: [Curdle] Which curves are MUST and SHOULD ?

Hubert Kario <hkario@redhat.com> Mon, 04 January 2021 16:53 UTC

Return-Path: <hkario@redhat.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 DEFBE3A0E7E for <curdle@ietfa.amsl.com>; Mon, 4 Jan 2021 08:53:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.469
X-Spam-Level:
X-Spam-Status: No, score=-0.469 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 (1024-bit key) header.d=redhat.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 gBCCel40C-9M for <curdle@ietfa.amsl.com>; Mon, 4 Jan 2021 08:53:46 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FDE43A0E7A for <curdle@ietf.org>; Mon, 4 Jan 2021 08:53:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1609779225; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VvVp/rYPYOt/8Zjaps4UrJSNy5lhBpSDmUCMOxzK/tA=; b=I5IrKXfLH30YyUIegBmPQy6+nv/U49nK0FUMBwG90Bk9d0BItWgXe50feob0fjIXLTFAiq YXB0Uqs9HuatadgocUNKpUscik7X5jTMzJKpkUEpGS504DIatVHCudm3gMt18y/0FuDkMS Q+bvJkftvzjJzg8QMYpBQBXhU7uFhEg=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-310-6Iq4hvhuPhiPrH5SZcggcA-1; Mon, 04 Jan 2021 11:53:43 -0500
X-MC-Unique: 6Iq4hvhuPhiPrH5SZcggcA-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6E40B9CC0D for <curdle@ietf.org>; Mon, 4 Jan 2021 16:53:42 +0000 (UTC)
Received: from localhost (unknown [10.40.208.38]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 091E97092D for <curdle@ietf.org>; Mon, 4 Jan 2021 16:53:40 +0000 (UTC)
From: Hubert Kario <hkario@redhat.com>
To: curdle@ietf.org
Date: Mon, 04 Jan 2021 17:53:38 +0100
MIME-Version: 1.0
Message-ID: <0f4dce32-b362-43d8-85e0-9608ca3427ab@redhat.com>
In-Reply-To: <40887.1608233724@eng-mail03>
References: <2CCABC30-F757-4659-9FF3-5AADDD51EE30@akamai.com> <4b681efd49274f03c7e0521e127e031426632ad0.camel@redhat.com> <CADZyTkk--kCWqE7q0Xi5C40V92MuZBktDzQGt_vPSZPiBy7v9w@mail.gmail.com> <18479.1606885358@eng-mail01.juniper.net> <20201205194724.GB64351@kduck.mit.edu> <37691.1607621661@eng-mail01.juniper.net> <1607647129866.76532@cs.auckland.ac.nz> <2917.1607672034@eng-mail01.juniper.net> <012AE120-2516-44F6-B729-ED342A137535@timeheart.net> <ED8F3B46-A5CC-4D14-A714-FD1C0AA67486@akamai.com> <12959BD6-F3AB-418B-8CE0-C3BE43999435@timeheart.net> <40887.1608233724@eng-mail03>
Organization: Red Hat
User-Agent: Trojita/0.7-git; Qt/5.14.2; xcb; Linux; Fedora release 32 (Thirty Two)
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=hkario@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/mOQYaRUddx2hLdNJ4wHtJjcAPyU>
Subject: Re: [Curdle] Which curves are MUST and SHOULD ?
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 04 Jan 2021 16:53:48 -0000

On Thursday, 17 December 2020 20:35:24 CET, Mark D. Baushke wrote:
> Ron Frederick <ronf@timeheart.net> writes:
>
>> On Dec 15, 2020, at 8:09 AM, Salz, Rich <rsalz@akamai.com> wrote:
>>>>   I’m not comfortable with algorithms going from REQUIRED to 
>>>> SHOULD NOT without some kind of transitional period. My 
>>>> suggestion would be to ease into this with SHOULD NOT for 
>>>> now. If you want to discuss BCP in this draft, perhaps that 
>>>> can be a separate section.
>>> 
>>> We've done it before, MD5, short RSA/DH keys, etc.
>>> 
>>> We shouldn't pretend that crypto-breaking advances haven't happened.
>>> 
>>> Admins can make trade-offs anyway.
>
> I am under the impression that the audience here is the maintainers of
> SSHv2 software rather than the administrators that manage the sites
> using it.

it's both
-- 
Regards,
Hubert Kario
Senior Quality Engineer, QE BaseOS Security team
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 115, 612 00  Brno, Czech Republic