Re: [netconf] ietf crypto types - permanently hidden

Kent Watsen <kent@watsen.net> Thu, 02 May 2019 16:59 UTC

Return-Path: <0100016a797c341a-0cde321d-e18f-4d8a-8b0b-2e89ed0ec458-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 2A3291204AA for <netconf@ietfa.amsl.com>; Thu, 2 May 2019 09:59:08 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] 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 cbE_xdzwz2MU for <netconf@ietfa.amsl.com>; Thu, 2 May 2019 09:59:05 -0700 (PDT)
Received: from a8-83.smtp-out.amazonses.com (a8-83.smtp-out.amazonses.com [54.240.8.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA6DB1204AC for <netconf@ietf.org>; Thu, 2 May 2019 09:59:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1556816344; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=fT4xCwvPNWQSzjm0LSY/5ZYqK/lgJv+kSRnIuyImtRM=; b=mJ2cfweV5N28mIQVO0PBuPcAcOiHoNebSDbeLs9JphkSYqx/NGNSdU79/UihYUnP oykBy4viP+e0sWSBvnxH9hcma+fQ3DvT87Vow2qVfXBy3glgdbruLt+449Cuh476lW1 FXBk+o/rClNpZZTaonhTZmH8w6fCLjps8i3h9aik=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Kent Watsen <kent@watsen.net>
In-Reply-To: <e30aa60f31ba40e8abc9cfaeffad7802@XCH-RCD-007.cisco.com>
Date: Thu, 2 May 2019 16:59:04 +0000
Cc: Martin Bjorklund <mbj@tail-f.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <0100016a797c341a-0cde321d-e18f-4d8a-8b0b-2e89ed0ec458-000000@email.amazonses.com>
References: <0100016a6e2130be-ee556dd0-e993-459f-be28-65fe1f74ece8-000000@email.amazonses.com> <20190430.144930.844252169549242587.mbj@tail-f.com> <20190430161223.cwqfsyyxbtnkqbl7@anna.jacobs.jacobs-university.de> <20190501.230622.158012882760210627.mbj@tail-f.com> <e30aa60f31ba40e8abc9cfaeffad7802@XCH-RCD-007.cisco.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-SES-Outgoing: 2019.05.02-54.240.8.83
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Wuwr0g4uvDhFYXNmVkHducPBoGQ>
Subject: Re: [netconf] ietf crypto types - permanently hidden
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, 02 May 2019 16:59:14 -0000

Hi Rob,

> Why is a separate action required to create the keys? 
> 
> Why is the configuration to generate a hidden key not sufficient for the device to automatically allocate a key in the TPM module?


I seem to be failing with words. 
Hopefully a picture will do the trick...



THIS IS WHAT WE HAVE CURRENTLY
==============================

                         |  Client is okay with the      |  Client is NOT okay with the  |
                         |  private key being in config  |  private key being in config  |
                         |  w/ nacm:default-deny-all.    |  i.e., wants "hidden" key.    |
                         |  (doc model not impacted.)    |  (doc model impacted!)        |
                         |  (this col more important)    |  (this col less important)    |
                         |                               |                               |
-------------------------+-------------------------------+-------------------------------+
                         |                               |                               |
Client is okay with      |                               |                               |
generating the private   |  <edit-config> can be used.   |  use <install-hidden-key>     |
key (not best practice)  |                               |                               |
                         |                               |                               |
-------------------------+-------------------------------+-------------------------------+
                         |                               |                               |
Client is NOT okay with  |                               |                               |
generating the private   |  Currently no solution !!!    |  use <generate-hidden-key>    |
key (best practice)      |                               |                               |
                         |                               |                               |
-------------------------+-------------------------------+-------------------------------+





PROPOSAL: move "hidden" from action names to an input parameter, and let an action gen config
=============================================================================================

                         |  Client is okay with the      |  Client is NOT okay with the  |
                         |  private key being in config  |  private key being in config  |
                         |  w/ nacm:default-deny-all.    |  i.e., wants "hidden" key.    |
                         |  (doc model not impacted.)    |  (doc model impacted!)        |
                         |  (this col more important)    |  (this col less important)    |
                         |                               |                               |
-------------------------+-------------------------------+-------------------------------+
                         |                               |                               |
Client is okay with      |  Either <edit-config> or      |  Use <install-key> with       |
generating the private   |  <install-key> with input     |  input "hidden".              |
key (not best practice)  |  NOT "hidden".                |                               |
                         |                               |                               |
-------------------------+-------------------------------+-------------------------------+
                         |                               |                               |
Client is NOT okay with  |  Use <generate-key> with      |  Use <generate-key> with      |
generating the private   |  with input NOT "hidden".     |  with input "hidden".         |
key (best practice)      |                               |                               |
                         |                               |                               |
-------------------------+-------------------------------+-------------------------------+



Other proposals welcomed.

Kent // contributor