Re: [saag] storing validation parameters on PKCS#8 formatted private keys
Brian Smith <brian@briansmith.org> Thu, 10 August 2017 12:21 UTC
Return-Path: <brian@briansmith.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5CE6132656 for <saag@ietfa.amsl.com>; Thu, 10 Aug 2017 05:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=briansmith-org.20150623.gappssmtp.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 XVWrHPvLHjGs for <saag@ietfa.amsl.com>; Thu, 10 Aug 2017 05:21:19 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 E2A91132125 for <saag@ietf.org>; Thu, 10 Aug 2017 05:21:18 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id 76so12003468ith.0 for <saag@ietf.org>; Thu, 10 Aug 2017 05:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=briansmith-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GXsgm45YEclD2wMyN8p1dlpUeA/Fd+HMVP6UHdMn2Fk=; b=W9K6IW7agP5E9C1CwVebXqDuDA6PXI5fnYxor0QLVYvDd33vGv81TaKOD9Wk0zQwgu 2ChvZ9qU8f8+KVnISHcQ+LY6jRLwXy107ji2VifaO/lq+m/pXKr6Vnd38chcwftzkS9G 8tpMmnj9QP38nQEbu1AO0TjVpOr4jlVtw7ocVO5iMQABW9rtT54xxbx9PtX/9tjlqrpD kV4DJWhR7IK/CsU11roLobN9vvUC8XfY9hzqRmbbqmiZ8ZvjT9B2kuvjpK2UE+ttN4sB DK9zKSift7g4xBGKOQESN2z3q1i281FSneJMPPNLUgkk4i+peG6Utb9KlijwrNAhoMBQ w9hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GXsgm45YEclD2wMyN8p1dlpUeA/Fd+HMVP6UHdMn2Fk=; b=QLp/uk2CP7QTf+qZcr4IYvCWeOh7MMdVv8hGVxVvIDh9sFxuhU0s9fb/ZHzDhMopiu vBPTjpRy5e4ktefbqwwp7Gefis2cIvwQOTsdkzxuY+mhBUMwWdMfkpUWKXpq1Bczkgv3 4dXM5A5mqY9gSMbsgWo2fi5l3DR9hYyaGIlsN+hs+dXExMcPCNxSubZBXfEhpuI3fKhI vOVMXClxB19nuho3vCBzpHIqEwNuQE4IDdw3BklSdlZe4L6cc0JfPdC6iIIhSudmNwnq PMzAb3eZRKldStt+vDtKR9SqRDdoWE4cObf1AFWq1YvWGQ+DOcNY24yTBTJNW5klwRTl Eeuw==
X-Gm-Message-State: AIVw1111+pO++dHVltem8UlymaQNfijg4+d7YgyLcUpEA3lgui9tL3ow 0H6mb7k3JNziplVbMtUwOjrGHn0cGJlZ
X-Received: by 10.36.40.147 with SMTP id h141mr4626428ith.85.1502367678299; Thu, 10 Aug 2017 05:21:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.222.86 with HTTP; Thu, 10 Aug 2017 05:21:17 -0700 (PDT)
In-Reply-To: <CAJU7zaJpRpp-DnjrwmekOb2BEMrPOrMnQrC3AdWoD8uJ6G7Muw@mail.gmail.com>
References: <CAJU7zaJpRpp-DnjrwmekOb2BEMrPOrMnQrC3AdWoD8uJ6G7Muw@mail.gmail.com>
From: Brian Smith <brian@briansmith.org>
Date: Thu, 10 Aug 2017 02:21:17 -1000
Message-ID: <CAFewVt6rsmgmqvndbgySWAboT3=xQyFgYhdbV03pkVF-NpvPcg@mail.gmail.com>
To: Nikos Mavrogiannopoulos <n.mavrogiannopoulos@gmail.com>
Cc: IETF SAAG <saag@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f67dcc9947e0556653b59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/l1C4r2RbsmLdrqH1aJdm1Y9GvRM>
Subject: Re: [saag] storing validation parameters on PKCS#8 formatted private keys
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Aug 2017 12:21:21 -0000
Nikos Mavrogiannopoulos <n.mavrogiannopoulos@gmail.com> wrote: > Hi, > I've needed to store parameters related to FIPS-186-4 provable key > generation validation in a PKCS#8 private keys for RSA (can be used > for DSA too if anyone cares). I've described the PKCS#8 extension at: > http://nmav.gitlab.io/draft-mavrogiannopoulos-pkcs8-validated-parameters/ > > The approach followed was simple, store the validation parameters as > an attribute, something that allows the keys to be backwards > compatible. I'd appreciate comments on the approach. > This format only supports one private key generation method, and also requires (IIUC) that the proof be generated at the time the key was generated. Why not instead define an attribute for storing a primality certificate? A primality certificate can be generated after-the-fact and for any (IIUC) key generation algorithm. Cheers, Brian -- https://briansmith.org/
- [saag] storing validation parameters on PKCS#8 fo… Nikos Mavrogiannopoulos
- Re: [saag] storing validation parameters on PKCS#… Russ Housley
- Re: [saag] storing validation parameters on PKCS#… Nikos Mavrogiannopoulos
- Re: [saag] storing validation parameters on PKCS#… Brian Smith
- Re: [saag] storing validation parameters on PKCS#… Nikos Mavrogiannopoulos