alecmuffett / certificate-transparency

Automatically exported from code.google.com/p/certificate-transparency
0 stars 0 forks source link

RFC6962-bis: Clarify which certs/SCTs an Auditor will actually encounter #32

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Section 3 says:
"Auditors can thus verify that each certificate for which an SCT has been 
issued indeed appears in the log."

This sentence seems to (wrongly) imply that an Auditor is guaranteed to see 
_every_ SCT that a Log issues.  In fact, an Auditor will only see the SCTs that 
it happens to encounter, and won't know how many SCTs remain unseen.

Suggested re-wording of that Section 3 paragraph:
"Periodically, each log appends all its new entries to the Merkle Tree and 
signs the root of the tree. The log MUST incorporate a certificate in its 
Merkle Tree within the Maximum Merge Delay period after the issuance of the 
SCT. When encountering an SCT, an Auditor can verify that the certificate was 
added to the Merkle Tree within that timeframe."

Original issue reported on code.google.com by robst...@gmail.com on 11 Feb 2014 at 1:10

GoogleCodeExporter commented 9 years ago
Makes sense - Ben, anything to add about the wording of the original sentence?

Original comment by er...@google.com on 11 Feb 2014 at 1:47

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Fixed in r16fdb7bee7db.

Original comment by benl@google.com on 18 Feb 2014 at 7:13

GoogleCodeExporter commented 9 years ago

Original comment by benl@google.com on 18 Feb 2014 at 7:13