IETF Logo Mail Archive

Re: [netconf] crypto-types fallback strategy

"Salz, Rich" <rsalz@akamai.com> Thu, 12 September 2019 17:02 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 336441208A7 for <netconf@ietfa.amsl.com>; Thu, 12 Sep 2019 10:02:34 -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, 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_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=akamai.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 nxnOJZVf_aIh for <netconf@ietfa.amsl.com>; Thu, 12 Sep 2019 10:02:32 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 09EFC12088A for <netconf@ietf.org>; Thu, 12 Sep 2019 10:02:32 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id x8CH2865014942; Thu, 12 Sep 2019 18:02:31 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=tFBM6APWQZeYjNuI9tpbSlHA86lpqJ5zvauyCgVc0go=; b=HHpMGPRBSZaRSDFpdzA2EHg5ZcU4iVXkRwquV05vOp2hWWsnAyX3CXN0NDvVqyxf7Vm4 ZYM+yqrMe499N7yuqp7wwlR7yjKHrKv0pC8C/6JqkJGeMbveCkvMnMJjyCSLuBKw6gDf TSUOJCKjGj5I14JnvTUvb6tC+kU64DcnH6cB2CxbNx9iA6Dfkilysf4roU1pvNk/YR3g GzyzQ0WyLD7W6JevGl41H1wjHzalRKf5JNNzWlNf2AzT0RbhzsIEgCflzJ37/J/SDaVk u0h9qvJpcOXEvwPG5VFXR1E93nlJ4tjFV49VF7r+A6ufxd099/rk3k08nH7nEeFjahDU 1A==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2uv434gk82-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 12 Sep 2019 18:02:30 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x8CGlZTd029526; Thu, 12 Sep 2019 13:02:29 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 2uv7vwaqan-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 12 Sep 2019 13:02:29 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 12 Sep 2019 13:02:28 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1473.005; Thu, 12 Sep 2019 13:02:27 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Kent Watsen <kent+ietf@watsen.net>, Martin Bjorklund <mbj@tail-f.com>
CC: "housley@vigilsec.com" <housley@vigilsec.com>, "netconf@ietf.org" <netconf@ietf.org>, "sean@sn3rd.com" <sean@sn3rd.com>, "rifaat.ietf@gmail.com" <rifaat.ietf@gmail.com>
Thread-Topic: [netconf] crypto-types fallback strategy
Thread-Index: AQHVaNxGVhFlbERW30moo9Q8WhnpJqcoBcwAgAB82YD//8NYgA==
Date: Thu, 12 Sep 2019 17:02:27 +0000
Message-ID: <65A6D989-0BA6-4755-AA76-21BACB8E0559@akamai.com>
References: <0100016d21ee2101-fb4f3288-1975-4a7d-a499-cb42ff8d9e14-000000@email.amazonses.com> <20190912.111242.323252506550752617.mbj@tail-f.com> <0100016d265824b0-313d5248-5aba-4b96-8f21-768be7784568-000000@email.amazonses.com>
In-Reply-To: <0100016d265824b0-313d5248-5aba-4b96-8f21-768be7784568-000000@email.amazonses.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.33.36]
Content-Type: multipart/alternative; boundary="_000_65A6D9890BA64755AA7621BACB8E0559akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-09-12_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=773 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1909120175
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.70,1.0.8 definitions=2019-09-12_09:2019-09-11,2019-09-12 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=754 adultscore=0 lowpriorityscore=0 mlxscore=0 clxscore=1011 priorityscore=1501 suspectscore=0 malwarescore=0 bulkscore=0 impostorscore=0 phishscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1909120178
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/OaAoLjBU6Z6VpRTOZSLmZjVQQKI>
Subject: Re: [netconf] crypto-types fallback strategy
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 17:02:37 -0000

You should not require every private key to have  the public key; they are often separated – e.g., most SSH implementations separate them. As you point out, they don’t share the same ASN1 data structures: a “25519” key is a bytestring, a DH key is two “bignums” (in OpenSSL terms), an RSA key is different from a DSA key, and so on.

I think saying “used by TLS” is not a good reason, we should really talk about the applications we are trying to configure and manage.  Or am I hopelessly wrong about netconf?  That could be likely, I’m only here for the crypto objects dicussions.

v2.23.0 | Report a Bug | By Email