<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
p.paragraph, li.paragraph, div.paragraph
{mso-style-name:paragraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.normaltextrun
{mso-style-name:normaltextrun;}
span.eop
{mso-style-name:eop;}
span.scxw53035567
{mso-style-name:scxw53035567;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">There have been a couple people discussing a limit of two per year, but those people are going beyond what I’ve been trying to get people to do, which as a reminder, is the 15<sup>th</sup> day of odd months. Easy to remember, and misses
most major holidays. Clint appears to have a different parity preference from my original proposal
<span style="font-family:"Segoe UI Emoji",sans-serif">😊</span> I don’t really care, as long as we have 6 instead of 366 possibilities. By having a date available every other month, no deadline ever has to move more than about 30 days to find an acceptable
date, and there are very few cases where 30 days difference in effective date actually matters in practice.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Tim<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Servercert-wg <servercert-wg-bounces@cabforum.org>
<b>On Behalf Of </b>Clint Wilson via Servercert-wg<br>
<b>Sent:</b> Friday, May 26, 2023 11:45 AM<br>
<b>To:</b> Tom Zermeno <tom@ssl.com>; ServerCert CA/BF <servercert-wg@cabforum.org><br>
<b>Subject:</b> Re: [Servercert-wg] SC-59 Weak Key Guidance<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Tom, Dimitris,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I continue to be opposed to the SCWG trying to limit effective dates to 2 per year. I think it’s entirely reasonable to align on a day of the month (I think the 15th has broadly been the only one I’ve heard proposed). I think it’s reasonable
to try to avoid January and December. I also think there may be value in trying to reduce the overall number of effective dates somewhat. The dates I’m personally in favor of aligning on are February, April, June, August, and October 15th.<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If there’s a particular penchant towards March and September, however, then I’d be unopposed to March, May, July, September, and November 15th. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">For this ballot in particular, I think October 15 or November 15 2023 are feasible targets for implementing these changes and would greatly prefer closing this issue (open now for
<u>more than 3 years</u>) sooner than later, especially given the number of incidents we’ve seen in the last years related to weak key vulnerabilities and CAs issuing certificates with weak keys.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-Clint<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On May 26, 2023, at 7:37 AM, Tom Zermeno via Servercert-wg <<a href="mailto:servercert-wg@cabforum.org">servercert-wg@cabforum.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hello Dimitris,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you for the input. We feel that September 15<sup>th</sup><span class="apple-converted-space"> </span>does not provide enough time for CAs to implement these changes, but we are not against the March 15,<span class="apple-converted-space"> </span><sup> </sup>2024
effective date, if there is consensus from the Community.<span class="apple-converted-space"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Tom<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://url.avanan.click/v2/___http:/ssl.com/___.YXAzOmRpZ2ljZXJ0OmE6bzozMmEwZjBiOWE3OGI4Mzg1M2JmYTg0MzJmNmQxNWU0Nzo2OjYzMjE6ZTQ4ZGE3N2YxMjg1M2NlYTFmOWIxOGZmMjg4MWUzNjVhOGYzZTY5ZGFjNDQ4ZTA3YTQwYzMxYWRlOWFiOWJlNDpoOkY" title="Protected by Avanan: http://ssl.com/">SSL.com</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentcolor currentcolor;border-image: none">
<div>
<p class="MsoNormal"><b>From:</b><span class="apple-converted-space"> </span>Servercert-wg <<a href="mailto:servercert-wg-bounces@cabforum.org">servercert-wg-bounces@cabforum.org</a>><span class="apple-converted-space"> </span><b>On Behalf Of<span class="apple-converted-space"> </span></b>Dimitris
Zacharopoulos (HARICA) via Servercert-wg<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Friday, May 26, 2023 1:54 AM<br>
<b>To:</b><span class="apple-converted-space"> </span><a href="mailto:servercert-wg@cabforum.org">servercert-wg@cabforum.org</a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [Servercert-wg] SC-59 Weak Key Guidance<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Hi Tom,<br>
<br>
Historically, the SCWG has been trying to avoid effective dates during January or December. I recommend using September 15, 2023 or March 15, 2024 as possible effective dates. These two dates seem to be<span class="apple-converted-space"> </span><a href="https://url.avanan.click/v2/___https:/docs.google.com/presentation/d/1oTGVYqggQpQMR4Lktbu_L6DhuBVJzeuiFGd9EAU1zsE___.YXAzOmRpZ2ljZXJ0OmE6bzozMmEwZjBiOWE3OGI4Mzg1M2JmYTg0MzJmNmQxNWU0Nzo2OjNhZDU6ZGYwZmJlNGYyMzU2OGZhMzM5MTRiNDliNDM5OWVjMTk5ZTNjNGZmODhhZDA1MjRkYzZkZmY4MzMxZjZiNjkwZjpoOkY" title="Protected by Avanan: https://docs.google.com/presentation/d/1oTGVYqggQpQMR4Lktbu_L6DhuBVJzeuiFGd9EAU1zsE">more
favorable</a><span class="apple-converted-space"> </span>than others.<span class="apple-converted-space"> </span><br>
<br>
<br>
Thanks,<br>
Dimitris.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On 25/5/2023 10:51 μ.μ., Tom Zermeno via Servercert-wg wrote:<o:p></o:p></p>
</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">Purpose of Ballot SC-059 V3</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">Several events within the community have led to concerns that the Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates (BRs) lacked a specificity
required to properly guide CAs on matters dealing with the identification and processing of digital certificates based on private keys considered weak, or easy to ascertain. In the hopes that elaboration and clarity on the subject would be beneficial to the
community, we are presenting updates to §4.9.1.1(“Reasons for Revoking a Subscriber Certificate) and §6.1.1.3 (Subscriber Key Pair Generation) of the BRs.</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">The first update is to §4.9.1.1 and is made to expand the scope of easily computable Private Keys from “Debian weak keys” to “those listed in section 6.1.1.3(5)”. While the initial
language in the BRs did not exclude other concerns, the use of a single example could be interpreted to mean that other easily computable Private Keys are few and far between. The next update was to §6.1.1.3(5), wherein we added specific actions to be taken
for ROCA vulnerability, Debian weak keys - both RSA and ECDSA – and Close Primes vulnerability. We also added a link to suggested tools to be used for checking weak keys. Finally, an implementation date of December 1, 2023 was added to allow CAs time to update
processes to meet the requirements.</span><span class="apple-converted-space"> </span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">The following motion has been proposed by Thomas Zermeno of</span><span class="apple-converted-space"> </span><span class="normaltextrun"><a href="https://url.avanan.click/v2/___http:/ssl.com/___.YXAzOmRpZ2ljZXJ0OmE6bzozMmEwZjBiOWE3OGI4Mzg1M2JmYTg0MzJmNmQxNWU0Nzo2OmFiNzE6MDc5MWRkN2IwNzFjY2Q1N2JkZDJlZDg4ZmViNTI4OTA0ZDRkOGRiNjA2NzYzNmQ3MmZlYjgzNzk3YmQ2OGNlMDpoOkY" title="Protected by Avanan: http://ssl.com/">SSL.com</a></span><span class="apple-converted-space"> </span><span class="normaltextrun">and
endorsed by Ben Wilson of Mozilla and Martijn Katerbarg of Sectigo.</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">--Motion Begins—</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun"><span style="font-size:12.0pt">This ballot is intended to clarify CA responsibilities regarding weak key vulnerabilities, including specific guidance for Debian weak key, ROCA
and Close Primes attack vulnerabilities, and modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates” as follows, based on Version 2.0.0.</span></span><span class="apple-converted-space"><span style="font-size:12.0pt"> </span></span><span class="scxw53035567"><span style="font-size:12.0pt"> </span></span><span style="font-size:12.0pt"><br>
<span class="scxw53035567"> </span><br>
<span class="normaltextrun">Notes: Upon beginning discussion for SC-59, the then-current version of the BRs was 1.8.4; since that time several ballots have been approved, leading to the increment of the version to 1.8.7 and eventually 2.0.0, which is the latest
approved version of the BRs. The changes introduced in SC-59 do not conflict with any of the recent ballots. As observed with other ballots in the past, minor administrative updates must be made to the proposed ballot text before publication such that the
appropriate Version # and Change History are accurately represented (e.g., to indicate these changes will be represented in Version 2.0.1).</span><span class="eop"> </span></span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun"> </span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">MODIFY the Baseline Requirements as specified in the following Redline:</span><span class="apple-converted-space"> </span><a href="https://url.avanan.click/v2/___https:/github.com/cabforum/servercert/compare/a0360b61e73476959220dc328e3b68d0224fa0b3...SSLcom:servercert:3b0c6de32595d02fbd96762cda98cdc88addef00___.YXAzOmRpZ2ljZXJ0OmE6bzozMmEwZjBiOWE3OGI4Mzg1M2JmYTg0MzJmNmQxNWU0Nzo2OjliZGQ6NjZkMTllYjUxZjYzMzZlMDZlOTUyMGQzNWU3NmFhMWYxOTNhYzg4ZGMyYWRlZWE5NGE3NWZlYTk3MTkzNjZhYzpoOkY" target="_blank" title="Protected by Avanan: https://github.com/cabforum/servercert/compare/a0360b61e73476959220dc328e3b68d0224fa0b3...SSLcom:servercert:3b0c6de32595d02fbd96762cda98cdc88addef00"><span class="normaltextrun">https://github.com/cabforum/servercert/compare/a0360b61e73476959220dc328e3b68d0224fa0b3...SSLcom:servercert:3b0c6de32595d02fbd96762cda98cdc88addef00</span></a><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun"> </span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">--Motion Ends—</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">This ballot proposes a Final Maintenance Guideline. The procedure for approval of this ballot is as follows:</span><span class="eop"> </span><o:p></o:p></p>
<p class="paragraph" style="vertical-align:baseline"><span class="normaltextrun">Discussion (11+ days) • Start time: 2023-05-25 19:00:00 UTC • End time: 2023-06-08 18:59:00 UTC</span><span class="scxw53035567"> </span><br>
<span class="normaltextrun">Vote for approval (7 days) • Start time: TBD • End time: TBD</span><span class="eop"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
</div>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Servercert-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:Servercert-wg@cabforum.org">Servercert-wg@cabforum.org</a><o:p></o:p></pre>
<pre><a href="https://url.avanan.click/v2/___https:/lists.cabforum.org/mailman/listinfo/servercert-wg___.YXAzOmRpZ2ljZXJ0OmE6bzozMmEwZjBiOWE3OGI4Mzg1M2JmYTg0MzJmNmQxNWU0Nzo2OjMwMTg6MTM1ZGYxYWE2NGNkNGI2ZDJmNjdlZDk0MjU1MTAwYmYxNGY5ZTRhNGYyNGMyMmExZTk3OWI4MDlkZWZhMWZlMTpoOkY" title="Protected by Avanan: https://lists.cabforum.org/mailman/listinfo/servercert-wg">https://lists.cabforum.org/mailman/listinfo/servercert-wg</a><o:p></o:p></pre>
</blockquote>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">_______________________________________________<br>
Servercert-wg mailing list<br>
</span><a href="mailto:Servercert-wg@cabforum.org"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">Servercert-wg@cabforum.org</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
</span><a href="https://url.avanan.click/v2/___https:/lists.cabforum.org/mailman/listinfo/servercert-wg___.YXAzOmRpZ2ljZXJ0OmE6bzozMmEwZjBiOWE3OGI4Mzg1M2JmYTg0MzJmNmQxNWU0Nzo2OjBhZTA6YjJkMzJhYzhlMGVlZTlmY2NiNWEyYzk0NDNmMGVjNjU5ZmFmNTllZGI5OTU0Y2QwNmE2M2UwNjUzMjM2N2U4OTpoOkY" title="Protected by Avanan: https://lists.cabforum.org/mailman/listinfo/servercert-wg"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">https://lists.cabforum.org/mailman/listinfo/servercert-wg</span></a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>