<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div>No. Cab forum guidelines only apply to certs issued after the effective date. There's nothing that requires revocation of certs issued prior to the effective date that lack the required entropy.</div>
</div>
<br>
<br>
"Brown, Wendy (10421)" <wendy.brown@protiviti.com> wrote:<br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Jeremy -<br>
One potential issue is if the Root Certificate was generated before the 20 bits of entropy became a requirement- are you really saying those CAs had to modify their root certificate retroactively?<br>
<br>
-----Original Message-----<br>
From: public-bounces@cabforum.org [<a href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>] On Behalf Of Jeremy Rowley<br>
Sent: Tuesday, February 9, 2016 5:15 PM<br>
To: Dimitris Zacharopoulos <jimmy@it.auth.gr>; public@cabforum.org<br>
Subject: Re: [cabfpub] Fwd: Discussion about RFC5280 and BR in Mozilla-dev-security<br>
<br>
What does it hurt to require RootCAs to have 20 bits of entropy in the serial? We certainly didn't create an exemption for entropy from the serial number. Plus it seems like a good indicator on whether your end entity certs and sub CAs will likely have 20
bits of entropy in the serial number, doesn't it?<br>
<br>
Jeremy<br>
<br>
-----Original Message-----<br>
From: public-bounces@cabforum.org [<a href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>] On Behalf Of Dimitris Zacharopoulos<br>
Sent: Tuesday, February 9, 2016 5:26 AM<br>
To: public@cabforum.org<br>
Subject: [cabfpub] Fwd: Discussion about RFC5280 and BR in Mozilla-dev-security<br>
<br>
<br>
Re-posting to the public list (and apologies for those receiving it twice).<br>
<br>
Begin forwarded message:<br>
<br>
<br>
Dear CA/B Forum members,<br>
<br>
There is a discussion in Mozilla-dev-security mailing list regarding the interpretation of some sections from the BR (mainly 7.1) and RFC5280 (mainly<br>
4.2.1) regarding the "serial number" of "trust anchors" (as defined in RFC5280). Now, trust anchors are usually self-signed certificates known as RootCA certificates.<br>
<br>
According to the verification algorithm, as described in RFC5280, "Trust anchors" are treated as input to the algorithm. This means that the serial number of the RootCA certificate is ignored, together with other elements (for example policy OIDs).<br>
<br>
Also, the BR required serial numbers to have 20bits of entropy to prevent hash collision attacks. Was there ever a requirement or intension for trust anchors to RootCA certificates to have 20bits of entropy?<br>
<br>
It would be interesting for people with good technical knowledge of RFC5280 and people who defined section 7.1 of the BR to engage in the public discussion in moz-dev-sec under thread "New requirement:certlint testing".<br>
<br>
<br>
Best regards,<br>
Dimitris Zacharopoulos.<br>
<br>
_______________________________________________<br>
Public mailing list<br>
Public@cabforum.org<br>
<a href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a><br>
NOTICE: Protiviti is a global consulting and internal audit firm composed of experts specializing in risk and advisory services. Protiviti is not licensed or registered as a public accounting firm and does not issue opinions on financial statements or offer
attestation services. This electronic mail message is intended exclusively for the individual or entity to which it is addressed. This message, together with any attachment, may contain confidential and privileged information. Any views, opinions or conclusions
expressed in this message are those of the individual sender and do not necessarily reflect the views of Protiviti Inc. or its affiliates. Any unauthorized review, use, printing, copying, retention, disclosure or distribution is strictly prohibited. If you
have received this message in error, please immediately advise the sender by reply email message to the sender and delete all copies of this message. Thank you.<br>
</div>
</span></font>
</body>
</html>