Re: [lamps] Double signatures

"Dr. Pala" <madwolf@openca.org> Thu, 20 September 2018 17:44 UTC

Return-Path: <madwolf@openca.org>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27DE7130DE9 for <spasm@ietfa.amsl.com>; Thu, 20 Sep 2018 10:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_HK_NAME_DR=0.01, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
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 Wgym7VD6mToU for <spasm@ietfa.amsl.com>; Thu, 20 Sep 2018 10:44:40 -0700 (PDT)
Received: from mail.katezarealty.com (mail.katezarealty.com [104.168.158.213]) by ietfa.amsl.com (Postfix) with ESMTP id DA18B12426A for <spasm@ietf.org>; Thu, 20 Sep 2018 10:44:39 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mail.katezarealty.com (Postfix) with ESMTP id A58593741042 for <spasm@ietf.org>; Thu, 20 Sep 2018 17:44:39 +0000 (UTC)
X-Virus-Scanned: amavisd-new at katezarealty.com
Received: from mail.katezarealty.com ([127.0.0.1]) by localhost (mail.katezarealty.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HMPS79t13-y8 for <spasm@ietf.org>; Thu, 20 Sep 2018 13:44:25 -0400 (EDT)
Received: from Maxs-MBP.cablelabs.com (unknown [192.160.73.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.katezarealty.com (Postfix) with ESMTPSA id 0B55937404AB for <spasm@ietf.org>; Thu, 20 Sep 2018 13:44:25 -0400 (EDT)
To: spasm@ietf.org
References: <005a01d44916$7c9cb560$75d62020$@x500.eu> <CAErg=HHhU9H-Ng8sUtXu2S+F0fr2tLOX6=8UR77gz0YLqtGyaA@mail.gmail.com> <004a01d44928$b1500d40$13f027c0$@augustcellars.com> <04ce01d4492a$39400ce0$abc026a0$@gmail.com> <003601d4499e$7c8be3b0$75a3ab10$@x500.eu> <BN6PR14MB110623B94ED97509FAE9F71283040@BN6PR14MB1106.namprd14.prod.outlook.com> <087c01d449db$c78e6350$56ab29f0$@gmail.com> <BN6PR14MB1106DBDE49673AED8E6C937383040@BN6PR14MB1106.namprd14.prod.outlook.com> <9A1A8BFC-9670-42EA-8D8D-B3DC2494CB95@cablelabs.com> <798ACAFB-7417-42F5-BF1C-6C0765606AC0@vigilsec.com> <af01c991-c052-37a8-a14e-aa432f05470d@cablelabs.com> <002001d44c42$80388fd0$80a9af70$@x500.eu> <9c5c57bdbd9b4fe4aee5040f319f46a2@XCH-ALN-010.cisco.com>
From: "Dr. Pala" <madwolf@openca.org>
Message-ID: <7edda3b2-7a45-83ca-b4d9-698dbb7ca8c3@openca.org>
Date: Thu, 20 Sep 2018 11:44:22 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <9c5c57bdbd9b4fe4aee5040f319f46a2@XCH-ALN-010.cisco.com>
Content-Type: multipart/alternative; boundary="------------999C640EE5E7C12534D43CC4"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/DKvm4yrF0Y-yKPRsT5hmbHzsXzw>
Subject: Re: [lamps] Double signatures
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2018 17:44:45 -0000

Hi Panos, all,

that is correct - since the new OIDs for the Key and the Signatures 
would be new, clients would fail since they do not know the "composite" 
algorithm :D

Although developing support for it should not be too difficult, the 
solution it is not meant to be backward compatible as we want 
applications to be able to fail if they do not even know they were 
supposed to generate or verify multiple signatures instead of just one.

 From a usage perspective, I am leaning towards the need for the owner 
of the certificates to generate signatures with all the keys, and for 
the entity that validates the signatures it should validate all the 
signatures it supports and may accept signatures even if it does not 
understand all the algorithms (this is more an application decision 
based on the risk and threat model).

As I said, this solution fits not only certificates, but also OCSP 
responses, CRLs, CMS, PKCS#7, etc. and that is part of what is 
interesting for us :D I still need to check what are the needed changes 
for other formats like PKCS#1/#8/#12 for storing the composite public 
and private keys (this part still missing), but I hope that solving that 
part will not be too difficult...

Cheers,
Max


On 9/20/18 7:26 AM, Panos Kampanakis (pkampana) wrote:
>
> Hi Max,
>
> To rephrase Eric’s question, would the CompositeKey+CompositeSig 
> proposal be backwards compatible with existing systems?
>
> I mean it gives you the change to use more than one algos in case you 
> don’t trust all of them. But an old client wouldn’t be able to just 
> use the traditional key+sig unless he was upgraded to understand 
> CompositeKey+CompositeSig and its OIDs, right?
>
> Panos
>
> *From:*Spasm [mailto:spasm-bounces@ietf.org] *On Behalf Of *Erik Andersen
> *Sent:* Friday, September 14, 2018 11:49 AM
> *To:* 'SPASM' <spasm@ietf.org>rg>; Directory list 
> <x500standard@freelists.org>
> *Subject:* Re: [lamps] Double signatures
>
> The double signature is intended as a migration tool.
>
> In the normal operation, only one signature is used (the native 
> signature). When it is realized that the signature algorithm will be 
> too week i some future, the migration period starts and an 
> alternative, assuming stronger signature is provided for those able to 
> handle it. Legacy systems will ignore this alternative signature. 
> After the migration period, there will be no alternative signature and 
> the new stronger signature will be the native signature.
>
> Does that make sense?
>
> Erik
>
> *Fra:*Massimiliano Pala [mailto:m.pala@cablelabs.com]
> *Sendt:* 12 September 2018 23:01
> *Til:* Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>>
> *Cc:* SPASM <spasm@ietf.org <mailto:spasm@ietf.org>>; Erik Andersen 
> <era@x500.eu <mailto:era@x500.eu>>
> *Emne:* Re: [lamps] Double signatures
>
> Hi Russ, all,
>
> my personal position is that the signer MUST use all the keys that 
> have digitalSignature set, the verifier shall verify all the 
> signatures for which it does have support for.
>
> The rationale for this is that if I certify a public key in the 
> certificate, you should be able to use the private key to generate the 
> signature, therefore the approach is the same as usual: sign with your 
> key. In this case, it just happens that to generate the signature you 
> have to generate multiple ones and then combine them together.
>
> For the application that verifies those signatures, it is always a 
> question of what is the threshold that is acceptable for the 
> application (in terms of risk) in case it does not support all of the 
> algorithms that are used to generate the composite signature. Ideally 
> it would verify all, but it may decide to verify less (at least one).
>
> I also saw the other e-mail from Jim on this topic and I think it 
> could be a good idea - the use of the two OIDs is another way to go to 
> codify the validation process required. Technically, that makes sense 
> to me, however I am conflicted as this approach requires that the 
> signer has an understanding of what the verifier's capabilities are... 
> I think that defining two OIDs for the signatures could still be 
> useful because the signer might then decide the 
> "recommended"/"intended" verification behavior... I can see some 
> use-cases that might have a composite key with { RSA, EC } and the 
> "Must-Verify-All" OID for the signature, and another use-case where we 
> have a composite key with { RSA, HASH-BASED } and for the signature 
> "Must-Verify-At-Least-One".
>
> Does this make sense?
>
> Cheers,
> Max
>
> On 9/12/18 6:12 AM, Russ Housley wrote:
>
>     Max:
>
>     During a transition to quantum-resistant signatures, a signer
>     wants to put a traditional signature and a quantum-resistant
>     signature on an object.  Given your description of keyUsage and
>     extendedKeyUsage, both would have the digitalSignature bit set.
>      How does a client know if just one or both signatures must be valid?
>
>     As Jim Schaad already said, RFC 5752 talks about this issue when a
>     CMS SignedData contains more than one SignerInfo.
>
>     Russ
>
>         On Sep 11, 2018, at 4:45 PM, Max Pala <M.Pala@cablelabs.com
>         <mailto:M.Pala@cablelabs.com>> wrote:
>
>         Hi All,
>
>         I am working on a similar - but different - solution, in
>         particular I solve the issue of (a) being able to combine more
>         than one public key, (b) only one (actually two) OIDs
>         required, and (c) simply the processing by re-utilizing the
>         same data structures we have today.
>
>         I particular, I define a “composite public key” and “composite
>         signature”.
>
>         The first one encodes in the key value’s BITSTRING the DER
>         value of the SEQUENCE of public keys (each of which is a the
>         subjectPublicKeyInfo structure) and uses a specific OID that
>         identifies the public key type. The parameters of the
>         compositeKey algorithm can be used to encode the keyUsage and
>         the extendedKeyUsage for each of the keys in the composite key.
>
>         The same approach is used for the “Composite Signature” case
>         where the value of the signature is the DER representation of
>         the SEQUENCE of signatures made with each of the keys.
>
>         As soon as I have some spare time, I will submit the draft -
>         maybe this could be discussed in Bangkok?
>
>         This simple idea allows us to have all the other procedures
>         related to PKIs work - this means we can combine ECC with RSA
>         or with a Quantum-Resistant algorithm (when finally available
>         and standardized). A step forward for the deployment of
>         hybrid-PKIs where multiple Lagos for keys can be used to
>         authenticate data, certs, revocation data, etc... we plan to
>         use this in our infrastructures to provide a transitional path
>         for post-Quantum transition and to further improve the
>         algorithm-agility capability of PKIs.
>
>         What do you think?
>
>         Cheers,
>
>         Max
>
>         ---
>
>         Cheers,
>
>         Max
>
>         On Sep 11, 2018, at 8:38 AM, Tim Hollebeek
>         <tim.hollebeek@digicert.com
>         <mailto:tim.hollebeek@digicert.com>> wrote:
>
>             Unfortunately, “not every combination needs to be covered”
>             introduces a lot of politics around choosing which
>             combinations “need to be covered”, a subject on which
>             inevitably not everyone agrees.  I would rather avoid all
>             those discussions and the unnecessary work they represent.
>
>             I personally don’t think a single AlgID which implies a
>             SEQUENCE of ALG IDs is an improvement over a SEQUENCE of
>             ALG IDs, or its moral equivalent.  For simple hybrid use
>             cases, there is also a lot of value in having the
>             classical algorithm ID being the same as it usually is, to
>             allow easier interoperability with older systems that
>             don’t understand the newer algorithms (and can blissfully
>             ignore them).
>
>             -Tim
>
>             *From:*Santosh Chokhani <santosh.chokhani@gmail.com
>             <mailto:santosh.chokhani@gmail.com>>
>             *Sent:*Tuesday, September 11, 2018 10:29 AM
>             *To:*Tim Hollebeek <tim.hollebeek@digicert.com
>             <mailto:tim.hollebeek@digicert.com>>; 'Erik Andersen'
>             <era@x500.eu <mailto:era@x500.eu>>; 'SPASM'
>             <spasm@ietf.org
>             <mailto:spasm@ietf.org>>;x500standard@freelists.org
>             <mailto:x500standard@freelists.org>
>             *Subject:*RE: [lamps] Double signatures
>
>             Thanks Tim.
>
>             There are ways to accommodate your concern.
>
>             One way to handle this is defining a single Alg ID A which
>             implies a SEQUENCE of ALG IDs and define the relying party
>             rules in terms of its ability to process one or all ALG IDs.
>
>             Another way to do this is not every combination needs to
>             be covered and the user community defines its own  Alg ID
>             Xi which maps to a SEQUENCE of ALG IDs.
>
>             *From:*Spasm [mailto:spasm-bounces@ietf.org]*On Behalf
>             Of*Tim Hollebeek
>             *Sent:*Tuesday, September 11, 2018 10:03 AM
>             *To:*Erik Andersen <era@x500.eu <mailto:era@x500.eu>>;
>             'SPASM' <spasm@ietf.org
>             <mailto:spasm@ietf.org>>;x500standard@freelists.org
>             <mailto:x500standard@freelists.org>
>             *Subject:*Re: [lamps] Double signatures
>
>             Doesn’t the combinatoric explosion render this completely
>             impractical?
>
>             You need N_c x N_pq algorithm identifiers just to handle
>             the simple hybrid use case where a single classical
>             algorithm is being used in conjunction with a single
>             post-quantum algorithm.
>
>             And there are people who want to use multiple post-quantum
>             algorithms to hedge against potential yet to be discovered
>             weaknesses in post-quantum algorithms.
>
>             I’m not really looking forward to trying to allocate or
>             manage O(N_c x N_pq^3) algorithm identifiers…
>
>             -Tim
>
>             *From:*Spasm <spasm-bounces@ietf.org
>             <mailto:spasm-bounces@ietf.org>>*On Behalf Of*Erik Andersen
>             *Sent:*Tuesday, September 11, 2018 3:10 AM
>             *To:*'SPASM' <spasm@ietf.org
>             <mailto:spasm@ietf.org>>;x500standard@freelists.org
>             <mailto:x500standard@freelists.org>
>             *Subject:*Re: [lamps] Double signatures
>
>             Hi Santosh,
>
>             You have proposed something like this before. It still
>             puzzling in my brain. As I understand, it requires that we
>             define a particular algorithm that has a parameter that
>             includes the things you suggest. It is worthy to be analysed.
>
>             Erik
>
>             *Fra:*Spasm [mailto:spasm-bounces@ietf.org]*På vegne
>             af*Santosh Chokhani
>             *Sendt:*10 September 2018 19:18
>             *Til:*'Jim Schaad' <ietf@augustcellars.com
>             <mailto:ietf@augustcellars.com>>; 'Ryan Sleevi'
>             <ryan-ietf@sleevi.com
>             <mailto:ryan-ietf@sleevi.com>>;era@x500.eu
>             <mailto:era@x500.eu>
>             *Cc:*'SPASM' <spasm@ietf.org
>             <mailto:spasm@ietf.org>>;x500standard@freelists.org
>             <mailto:x500standard@freelists.org>
>             *Emne:*Re: [lamps] Double signatures
>
>             Why not let algorithm identifier dictate the number of
>             signatures and their syntax?
>
>             *From:*Spasm [mailto:spasm-bounces@ietf.org]*On Behalf
>             Of*Jim Schaad
>             *Sent:*Monday, September 10, 2018 1:07 PM
>             *To:*'Ryan Sleevi' <ryan-ietf@sleevi.com
>             <mailto:ryan-ietf@sleevi.com>>;era@x500.eu
>             <mailto:era@x500.eu>
>             *Cc:*'SPASM' <spasm@ietf.org
>             <mailto:spasm@ietf.org>>;x500standard@freelists.org
>             <mailto:x500standard@freelists.org>
>             *Subject:*Re: [lamps] Double signatures
>
>             Ryan,
>
>             The discussion in London dealt with a completely different
>             proposal than this one. While I think there are problems
>             with this that need to be dealt with they are mostly not
>             the same set.
>
>             Erik,
>
>             Why is this considered to be a preferred solution to
>             defining a new signature algorithm which contains as the
>             parameter the sequence of algorithm identifiers and as the
>             signature value a sequence of signature values.  The
>             problem with just defining the extension to SIGNED is that
>             one needs to make sure that the set of signature
>             algorithms and parameters are also part of the data to be
>             signed and I am not seeing that highlighted here.
>
>             Jim
>
>             *From:*Spasm <spasm-bounces@ietf.org
>             <mailto:spasm-bounces@ietf.org>>*On Behalf Of*Ryan Sleevi
>             *Sent:*Monday, September 10, 2018 8:53 AM
>             *To:*era@x500.eu <mailto:era@x500.eu>
>             *Cc:*SPASM <spasm@ietf.org
>             <mailto:spasm@ietf.org>>;x500standard@freelists.org
>             <mailto:x500standard@freelists.org>
>             *Subject:*Re: [lamps] Double signatures
>
>             On Mon, Sep 10, 2018 at 10:56 AM Erik Andersen
>             <era@x500.eu <mailto:era@x500.eu>> wrote:
>
>                 Hi Folk,
>
>                 In ITU-T we have plans to allow for double signatures
>                 using the SIGNED parametrized data type defined in
>                 X.509 to cope with situation as described in the
>                 internet draft: “Multiple Public-Key Algorithm X.509
>                 Certificates (draft-truskovsky-lamps-pq-hybrid-x509-01)”
>
>                 We suggest to enhance the SIGNED data type as shown below:
>
>                 *SIGNED{ToBeSigned} ::= SEQUENCE {*
>
>                 *COMPONENTS OF SIGNATURE,*
>
>                 *.......**,*
>
>                 *altAlgorithmIdentifier
>                 AlgorithmIdentifier{{SupportedAlgorithms}} OPTIONAL,*
>
>                 *altSignature BIT STRING OPTIONAL *
>
>                 ***}****(WITH COMPONENTS {..., altAlgorithmIdentifier
>                 PRESENT, altSignature PRESENT } |*
>
>                 *WITH COMPONENTS {..., altAlgorithmIdentifier ABSENT,
>                 altSignature ABSENT } )*
>
>                 **
>
>                 We are open to comments. We know that IETF is not a
>                 heavy user of this data type.
>
>                 We have no intention to use this extended data type
>                 for certificates and CRLs.
>
>                 For your information, SIGNATURE is defined as:
>
>                 *SIGNATURE ::= SEQUENCE {*
>
>                 *algorithmIdentifier
>                 AlgorithmIdentifier{{SupportedAlgorithms}},*
>
>                 *signature BIT STRING,*
>
>                 *....... }*
>
>             From the discussions in London (101), there were a number
>             of challenges identified during the discussion -
>             https://datatracker.ietf.org/meeting/101/materials/minutes-101-lamps-01.txt-
>             that fundamentally questioned that approach.
>
>             Has the ITU-T addressed or resolved those concerns? Are
>             they not applicable for some reason specific to ITU-T?
>
>         _______________________________________________
>         Spasm mailing list
>         Spasm@ietf.org <mailto:Spasm@ietf.org>
>         https://www.ietf.org/mailman/listinfo/spasm
>
> -- 
>
> Best Regards,
>
> Massimiliano Pala, Ph.D.
>
> CableLabs
> Principal Architect
> Security Services, R&D
>
>
>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm