IETF Logo Mail Archive

Re: [netconf] truststore usage in ietf-ssh/tls-client/server

Kent Watsen <kent+ietf@watsen.net> Wed, 09 October 2019 14:56 UTC

Return-Path: <0100016db1055a53-f9a7573e-5f0b-4d43-a952-959977378d2f-000000@amazonses.watsen.net>
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 65A851200E0 for <netconf@ietfa.amsl.com>; Wed, 9 Oct 2019 07:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 98NzyL20Eb1Z for <netconf@ietfa.amsl.com>; Wed, 9 Oct 2019 07:56:22 -0700 (PDT)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com [54.240.8.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C39812008B for <netconf@ietf.org>; Wed, 9 Oct 2019 07:56:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1570632981; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=5BdwqGpDh7vWHahp02YaFWlaSfeyyQ93BsrkT8F13Qg=; b=hjTJxSflBNPOoWN+kTlCjXUKfYFfXvFZ1X6oSeTBMYMRwCjtYUZdPQl7LcF78dj7 Pecm58sGNaBAvpMIPX+SCHwuhQeJ1OB23rdE/Z6HOLvDEgFEvqZZD6jZHiOdQwGXqRT 9Jh1n1rGr2Eye6vk1SAoEyzJA9Qcg57dsMLRTK0c=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016db1055a53-f9a7573e-5f0b-4d43-a952-959977378d2f-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5BF284BE-7310-4AFB-A164-E5EA10ED731B"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 09 Oct 2019 14:56:21 +0000
In-Reply-To: <AM0PR07MB51875014434A6F0676198C7283950@AM0PR07MB5187.eurprd07.prod.outlook.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, "netconf@ietf.org" <netconf@ietf.org>
To: Balázs Kovács <balazs.kovacs@ericsson.com>
References: <AM0PR07MB51879334FAD36D55675307E3839E0@AM0PR07MB5187.eurprd07.prod.outlook.com> <0100016da755ddce-18e94501-441b-471d-af1e-03ba88fde0ba-000000@email.amazonses.com> <AM0PR07MB51877236CE073078C5B90F9A839A0@AM0PR07MB5187.eurprd07.prod.outlook.com> <0100016dad284c4d-821b1403-49d4-41bb-87bf-275f611e6fe1-000000@email.amazonses.com> <E2A52BEB-FDA0-4F3B-A11F-052BD7A68120@akamai.com> <AM0PR07MB51875014434A6F0676198C7283950@AM0PR07MB5187.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.10.09-54.240.8.96
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/bzsdygAhXknAXrvQk6Hz0Udbtn0>
Subject: Re: [netconf] truststore usage in ietf-ssh/tls-client/server
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: Wed, 09 Oct 2019 14:56:24 -0000

Hi Balazs,

> I’m also rather in favor of ca-certs, especially if “trust anchor” means the root CA. Also in development the term CA certificate is much more understandable. I think the type allows a CA chain or one could use these leaves for partial chain validation too.

Noted.


>  Regarding the presence containers, if local-or-truststore-* have mandatory choice then I think you need to make the local-or-keystore-* containers also presence.

I just looked and all seems proper.  The local-or-keystore-* containers are required, as they hold or reference the obligatory private key.


Kent // contributor

v2.23.0 | Report a Bug | By Email