Re: [Trans] Prior knowledge of certificate serial number

Rick Andrews <> Wed, 24 September 2014 19:42 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id A04231A035E for <>; Wed, 24 Sep 2014 12:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.986
X-Spam-Status: No, score=-4.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lKqXOcBaPtVC for <>; Wed, 24 Sep 2014 12:42:30 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 904BC1A0351 for <>; Wed, 24 Sep 2014 12:42:30 -0700 (PDT)
X-AuditID: a66201d1-f796d6d0000009b9-74-54231ea40e12
Received: from ( []) by (Symantec Brightmail Gateway out) with SMTP id 09.22.02489.4AE13245; Wed, 24 Sep 2014 19:42:28 +0000 (GMT)
Received: from [] (helo=TUS1XCHHUBPIN03.SYMC.SYMANTEC.COM) by with esmtp (Exim 4.76) (envelope-from <>) id 1XWsSI-0001Gc-N3; Wed, 24 Sep 2014 15:42:26 -0400
Received: from TUS1XCHEVSPIN33.SYMC.SYMANTEC.COM ([]) by TUS1XCHHUBPIN03.SYMC.SYMANTEC.COM ([]) with mapi; Wed, 24 Sep 2014 12:42:24 -0700
From: Rick Andrews <>
To: Erwann Abalea <>
Date: Wed, 24 Sep 2014 12:42:22 -0700
Thread-Topic: [Trans] Prior knowledge of certificate serial number
Thread-Index: Ac/YLDIReNveuINDQYSYPl89mOh7ewAAfivw
Message-ID: <544B0DD62A64C1448B2DA253C011414607D14080F3@TUS1XCHEVSPIN33.SYMC.SYMANTEC.COM>
References: <> <544B0DD62A64C1448B2DA253C011414607D1408063@TUS1XCHEVSPIN33.SYMC.SYMANTEC.COM> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_544B0DD62A64C1448B2DA253C011414607D14080F3TUS1XCHEVSPIN_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCIsWRmVeSWpSXmKPExsWyLInRTXeJnHKIwcwXshYb5rxltmhrm8Vi sfbxRRYHZo+ds+6yeyxZ8pMpgCmKyyYlNSezLLVI3y6BK+Pr7XVMBadqK27u28HawDijqouR k0NCwETi0b/5rBC2mMSFe+vZuhi5OIQE3jFKtE7dxgLhvGKUOHf9MRNIlZDAKkaJt9ulQGw2 AT2JLY+vsIPYIgKqErdP3gObxCzgJ9G1fx4ziM0CFL+06B4biC0s4ChxYvklVoh6J4npXzqh eo0kVm5bBWbzCkRJ9PQ+ZIdYfIBR4t6740BXcHBwCgRKzNkpDlLDCHTp91NrmCB2iUvcejKf CeIDAYkle84zQ9iiEi8f/2OFqBeVuNO+nhGiPl/i6M+1bBC7BCVOznzCAlEvKXFwxQ2WCYzi s5CMnYWkZRaSlllAFzELaEqs36UPUaIoMaX7ITuErSHROmcuO7L4Akb2VYwyqck5hrklifml JQWpFQaGesWVuYnAmE3WS87P3cQIiduLOxgvHNY9xCjAwajEw3tQUjlEiDWxDKjyEKMEB7OS CK/KR6UQId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rwpIRwhQgLpiSWp2ampBalFMFkmDk6pBkbv /T233dbxW966uuB/6kLfGdccIj6zct7IEZvkv2U3oyIr67vFM7dLda8Vv33h4Exnhs5X1yuV pNbvPz1zU6+flZK6qozZ0862G3tPzP+37E23g2rj9NUpxUI/V+XcDlj8eVm28MHzBicnZtxn jjjs0Nc6JYRX65rcBME000O/BDg8bml8vFqmxFKckWioxVxUnAgAKKXy1NcCAAA=
Cc: Melinda Shore <>, "" <>
Subject: Re: [Trans] Prior knowledge of certificate serial number
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 24 Sep 2014 19:42:33 -0000


Isn’t it possible that I log a Precertificate in one or more log servers and then can’t issue the final certificate, either because of log server failure or failure of my issuance system? The log server records my INTENT to issue a certificate, but I don’t think it COMPELS me to issue that certificate. I must be able to reject that order, change the date and serial number and start over.

We worked around the issuerName+serialNumber constraint by storing certificates in one table, Precertificates in another.


From: Erwann Abalea []
Sent: Wednesday, September 24, 2014 12:18 PM
To: Rick Andrews
Cc: Melinda Shore;
Subject: Re: [Trans] Prior knowledge of certificate serial number

Bonsoir Rick,

If the dates set in the final certificate is different than the dates used in the Precertificate, the browser won't be able to verify the SCT. That means that all the Precertificates you publish for the same final certificate MUST be identical in every aspect.

We also have an issuerName+serialNumber constraint in database, that's why Option 1 isn't an easy task.

2014-09-24 21:05 GMT+02:00 Rick Andrews <<>>:

At Symantec we know the serial number prior to issuance, because we generate it and put it in the TBSCertficate.

The only problem we have with serial numbers is in the case where we fail to get enough SCTs to put in the cert. We'll retry the operation up to 48 hours, but we always want to set the notBefore date to the day we issue the cert, so we don't short-change customers (believe me, there are customers who notice). But if we update the notBefore date and retry the logging operation, we have to change the serial number too. Otherwise we might log different certs with the same serial number in different logs, and that would be inconsistent. However, we use the combination of issuer name and serial number as a unique key for that order in our database, so changing serial numbers is challenging. The simpler alternative is to reject the order and ask the customer to start over, but that's a bad customer experience. We're not sure yet how we'll solve this, but we'll figure something out (we don't expect 6962-bis to provide a solution). And while we hope that this situation will occur very rarely
 , it could happen, so we're preparing for it.


-----Original Message-----
From: Trans [<>] On Behalf Of Melinda Shore
Sent: Tuesday, September 23, 2014 9:08 AM
Subject: [Trans] Prior knowledge of certificate serial number

One of the questions that's come up is whether or not it's reasonable to expect that CAs will (or can) have knowledge of a certificate's serial number prior to issuance - it's one of the basic questions that needs to be considered in the context of the precertificate discussions.
We'd be grateful if any CAs (particularly ones with a CT implementation either in the works or planned) could give some feedback on that.



Trans mailing list<>

Trans mailing list<>