Re: [lamps] Double signatures

Max Pala <> Tue, 11 September 2018 20:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 81FBE130EB5 for <>; Tue, 11 Sep 2018 13:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6VFCQfhnoIa5 for <>; Tue, 11 Sep 2018 13:45:44 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fe50::717]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9BBD0130DE4 for <>; Tue, 11 Sep 2018 13:45:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BIGnciRCCfC2TTRcVu7d7sDEkF0igfR4TwAILBiwJPU=; b=Lxrz04FJDYGOeZ9htQ9YSfDXHWD2VzkCAe7w5K8T6rxgz5nW09VQHf3oNNG1WEDRqrwDhA7xU0GFev4UCYclSsa3zvthZuNJfcz25voPzA6HC4ojyCdbsld+T3BBM5B3nCl5wP24s539SqnaSQrC9sSfDnx/lq7Ce5ygTGvIyVo=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1122.18; Tue, 11 Sep 2018 20:45:41 +0000
Received: from ([fe80::8d2f:1182:1ded:7ba0]) by ([fe80::8d2f:1182:1ded:7ba0%5]) with mapi id 15.20.1122.019; Tue, 11 Sep 2018 20:45:41 +0000
From: Max Pala <>
To: Tim Hollebeek <>
CC: Santosh Chokhani <>, Erik Andersen <>, SPASM <>, "" <>
Thread-Topic: [lamps] Double signatures
Thread-Index: AQHUShBhJkT9zFJJ00iNdlz6b4VNfA==
Date: Tue, 11 Sep 2018 20:45:41 +0000
Message-ID: <>
References: <005a01d44916$7c9cb560$75d62020$> <> <004a01d44928$b1500d40$13f027c0$> <04ce01d4492a$39400ce0$abc026a0$> <003601d4499e$7c8be3b0$75a3ab10$> <> <087c01d449db$c78e6350$56ab29f0$> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: [2607:fb90:a6e5:8560:acfd:b9c5:119a:6fe8]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN6PR06MB4765; 20:zmaD4sAxNGpkhFu4WkFiW+2NimYaE+mzTQL0ETsL5VOn/l+wn+VLcSq7F/smNfvY5E4cObeXz1qjoySwz6CJlEItSsfcPXwsWNi5TM/eq5svZGnbGrwjWYPxQ/rnSw3PB2f8iNMlCkNXvRpf86UCZpTHUCI8cdQGLn1T18HB2pE=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 742cd635-5c61-408e-515d-08d6182789ef
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:SN6PR06MB4765;
x-ms-traffictypediagnostic: SN6PR06MB4765:
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(120809045254105)(85827821059158);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231311)(944501410)(52105095)(10201501046)(3002001)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123564045)(20161123562045)(201708071742011)(7699050); SRVR:SN6PR06MB4765; BCL:0; PCL:0; RULEID:; SRVR:SN6PR06MB4765;
x-forefront-prvs: 0792DBEAD0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39850400004)(136003)(376002)(346002)(396003)(189003)(53754006)(199004)(7736002)(229853002)(105586002)(5660300001)(6436002)(6486002)(14454004)(99286004)(25786009)(966005)(6246003)(4326008)(36756003)(2616005)(476003)(86362001)(14444005)(2906002)(11346002)(256004)(68736007)(97736004)(8676002)(83716003)(6916009)(446003)(46003)(486006)(5250100002)(54906003)(33656002)(561944003)(6506007)(82746002)(53546011)(81156014)(606006)(2900100001)(316002)(81166006)(6306002)(8936002)(6512007)(478600001)(236005)(72206003)(39060400002)(53936002)(76176011)(186003)(6116002)(93886005)(790700001)(102836004)(54896002)(106356001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR06MB4765;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-microsoft-antispam-message-info: kAu2xsV6kRTkh3Y3XVn+uuuvKJGwlLYW4sXfCv2Q3qPyI7xykBrpbGO1MzmyZs3CPgiZeByEAWG9lj0UgcEhuYFXHg8yRHNqzgCleM1UJtVazSVRH2rilK1Tx9I8uCCzFoxoBm1FFjBJhx2Da2vObkVNqeJukISFf3HPy4kMaM1VkGVipu40IOwM5wSG/tZ5EelSrqxQk1O/ScPx6olubmaddEROg7lfyGVHWqeyjYm1xVFnWTaZzY8fcyk75XyxQPgzXgU3AvYJPTVV8bEL4IIbmtuT6VBkzi1ppjIxZVMyzlzy6S+BUwUqjE9YoEutTiow6DLenWTCMjHWdine2TPYEM3UX4Y2H64MwMSwQHo=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_9A1A8BFC967042EA8D8DB3DC2494CB95cablelabscom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 742cd635-5c61-408e-515d-08d6182789ef
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Sep 2018 20:45:41.5036 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR06MB4765
Archived-At: <>
Subject: Re: [lamps] Double signatures
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 11 Sep 2018 20:45:49 -0000

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?



On Sep 11, 2018, at 8:38 AM, Tim Hollebeek <<>> 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).


From: Santosh Chokhani <<>>
Sent: Tuesday, September 11, 2018 10:29 AM
To: Tim Hollebeek <<>>; 'Erik Andersen' <<>>; 'SPASM' <<>>;<>
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 [] On Behalf Of Tim Hollebeek
Sent: Tuesday, September 11, 2018 10:03 AM
To: Erik Andersen <<>>; 'SPASM' <<>>;<>
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…


From: Spasm <<>> On Behalf Of Erik Andersen
Sent: Tuesday, September 11, 2018 3:10 AM
To: 'SPASM' <<>>;<>
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.


Fra: Spasm [] På vegne af Santosh Chokhani
Sendt: 10 September 2018 19:18
Til: 'Jim Schaad' <<>>; 'Ryan Sleevi' <<>>;<>
Cc: 'SPASM' <<>>;<>
Emne: Re: [lamps] Double signatures

Why not let algorithm identifier dictate the number of signatures and their syntax?

From: Spasm [] On Behalf Of Jim Schaad
Sent: Monday, September 10, 2018 1:07 PM
To: 'Ryan Sleevi' <<>>;<>
Cc: 'SPASM' <<>>;<>
Subject: Re: [lamps] Double signatures


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.


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.


From: Spasm <<>> On Behalf Of Ryan Sleevi
Sent: Monday, September 10, 2018 8:53 AM
Cc: SPASM <<>>;<>
Subject: Re: [lamps] Double signatures

On Mon, Sep 10, 2018 at 10:56 AM Erik Andersen <<>> 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:

  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:

  algorithmIdentifier  AlgorithmIdentifier{{SupportedAlgorithms}},
  signature            BIT STRING,
  ...... }

From the discussions in London (101), there were a number of challenges identified during the discussion - - 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?