<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
> When creating a new repository, the GitHub UI provides the option to "import your project to GitHub". I'm happy to fork if that is the preferred approach.<br>
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Of those two options I'd prefer forking, so that the origin is clear and so that it's easier to pull in any future upstream changes.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
> I would prefer to reference the raw keys in the BRs and allow CAs the flexibility to determine the format they want to use in their checks.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Makes sense.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 16px; color: rgb(0, 0, 0);">
<span style="background-color: rgb(255, 255, 255);">I suppose we could always provide links in the github.com/cabforum/Debian-weak-keys README to other repositories that (claim to) hold alternative, more compact checking formats for the same key material.</span></div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div style="direction: ltr; font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<b>From:</b> Wayne Thayer <wthayer@gmail.com><br>
<b>Sent:</b> 17 April 2024 00:46<br>
<b>To:</b> Rob Stradling <rob@sectigo.com><br>
<b>Cc:</b> Clint Wilson <clintw@apple.com>; CA/B Forum Server Certificate WG Public Discussion List <servercert-wg@cabforum.org><br>
<b>Subject:</b> Re: [Servercert-wg] Compromised/Weak Keys Ballot Proposal</div>
<div style="direction: ltr;"> </div>
<div style="text-align: left; line-height: 12pt; background-color: rgb(250, 250, 3); padding: 2pt; border-width: 1pt; border-style: solid; border-color: rgb(0, 0, 0); font-family: Calibri; font-size: 10pt;">
<span style="color: rgb(0, 0, 0);">CAUTION:</span><span style="color: black;"> This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.</span></div>
<br>
<div style="direction: ltr;">On Tue, Apr 16, 2024 at 3:23 PM Rob Stradling <<a href="mailto:rob@sectigo.com" id="OWAae894936-827a-44cf-a147-11599b67068b" class="OWAAutoLink" data-loopstyle="linkonly">rob@sectigo.com</a>> wrote:</div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
> Rob Stradling: I would like to import your repo to <a href="http://github.com/cabforum/Debian-weak-keys" id="OWA6e56b00d-9db9-dac0-9725-0ca96fe437d0" class="OWAAutoLink" shash="rsdYVvFj1LfqRx6JI666+7HoR4Smr+GCbdiXGwMYPoFoKOBBwcZ1aTiFM8Wvwbb8z3AxRrdmylBjr9BugmlY9yg3x2jqDnFLbVs2OOp7H0xatY9yqBJADsyS7iH9vdfQAYMKRQRot/yoDCFkISAZj2GHSHNM+JSh7aXfNQmAAD8=" originalsrc="http://github.com/cabforum/Debian-weak-keys" data-auth="Verified" data-loopstyle="linkonly">
github.com/cabforum/Debian-weak-keys</a>. May I have your permission to do so?</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Wayne. I put together the repositories at <a href="https://github.com/CVE-2008-0166" id="OWA8c1c0b24-333b-36b2-e92a-c8b5edc331f8" class="OWAAutoLink" shash="XdvFtDhqzPkKRkByqPgMXkoUDU9QkL+gQjBuvN3x/71Zy4o4QxSV7QEmkMYKKAC+PQy5BwjMG8m9jI+eejJsiwZNK/VO3AgbtQb46MOCB3Cq1znSlFVMuH8cPPZugsI3SkeZBYtzR/8wnER9d5tBUIqElXA1w9djXlq44Zvc+II=" originalsrc="https://github.com/CVE-2008-0166" data-auth="Verified" data-loopstyle="linkonly">
https://github.com/CVE-2008-0166</a> a few years ago with the sole aim of providing a resource that would help CAs comply with the original version of this draft ballot, so I have no hesitation in giving my permission for CABForum to use these repositories
in whatever way(s) are felt to make sense.</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">Thank you Rob.</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
There are currently 3 repositories under the <a href="https://github.com/CVE-2008-0166" id="OWA0d20b627-47f9-b1dc-0e98-4f84b53f104b" class="OWAAutoLink" shash="xShfX/dWAz2//hD03VudWkNdUmOI4Fa8uIKe6G3WTC3m6PNA8Z6UNdcT8n71LoBtPlG3yk2Ihx29sWWdH9dVeCrWsv1OeRsrJsHK8uON+d9H8aJtpnETUmSkn3xzLS93SEQsciYYZhnXyBDFMWmTU+FCD0HMLiwONtdZ0DPdFw8=" originalsrc="https://github.com/CVE-2008-0166" data-auth="Verified" data-loopstyle="linkonly">
https://github.com/CVE-2008-0166</a> GitHub organization: key_generator, private_keys, and openssl_blocklists. Which of these are you looking to "import" (fork?) into
<a href="https://github.com/cabforum" id="OWA45e92738-54c6-62fb-467a-25c423533ff0" class="OWAAutoLink" shash="hYr29AWinXOb/c0/xFn9oMqJplk0K5K9slzNL/8ASpiuvNEcrvVNleN67RWi5QCGAaX52xGdPF73Ie19yWzCKUVzoAxzpJb42j3yyxNXmwDBKDwLIfv4Jj+j8H+LgxK2ahxBVFGBBeKhfNV4fAedenwicSq2XesuzUTD+Z+67hg=" originalsrc="https://github.com/cabforum" data-auth="Verified" data-loopstyle="linkonly">
https://github.com/cabforum</a> ?</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">The intent of the ballot is to reference a set of weak keys, so my intention is to host the contents of your private_keys repository in the cabforum GitHub organization.</div>
<div style="direction: ltr;"><br>
</div>
<div class="elementToProof" style="direction: ltr;">When creating a new repository, the GitHub UI provides the option to "import your project to GitHub". I'm happy to fork if that is the preferred approach.</div>
<div class="elementToProof" style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
key_generator is useful if anyone wants to check my work, or if Debian weak keys of any other sizes need to be generated in the future.</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
private_keys holds the generated keys. Cloning this repository requires 12GB of disk space (just over 3GB for each of the 3 architectures, plus another 3GB for the ".git" directory)! Although each of the generated RSA keys has the public exponent 65537, it's
important to note that every public exponent is equally vulnerable when used with a vulnerable modulus (as described in the key_generator
<a href="https://github.com/CVE-2008-0166/key_generator?tab=readme-ov-file#pregenerated-keys-and-blocklists" id="OWAa460e54f-4f24-d8dc-68a3-dc480c11add4" class="OWAAutoLink" title="https://github.com/CVE-2008-0166/key_generator?tab=readme-ov-file#pregenerated-keys-and-blocklists" shash="xFZ/L6vE7jTn7DNcL2xxQ3aIxREVCBGaFnD0uiHau/LFJM1yMQYjElKGVZZn3ASpbOOjFau4d4nYocRx/lv9yUSIpU9/1oELuebYReOmqMJjQ+tOZZYAlO5aEDu70bEg0teg0nHqrWxeHrMFBAaMokXuhdB+HqAH1Ea2kElizGw=" originalsrc="https://github.com/CVE-2008-0166/key_generator?tab=readme-ov-file#pregenerated-keys-and-blocklists" data-auth="Verified" data-loopstyle="linkonly">
README</a>).</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
openssl_blocklists holds blocklists of the generated keys that are compatible with the openssl_vulnkey tool that was made available by Debian back in 2008. Only the weak RSA keys are supported, because openssl_vulnkey's file format is basically a list of
SHA-1 hashes of RSA moduli. Cloning this repository requires a mere 84MB of disk space though (18MB for each of the 3 architectures, plus 32MB for the ".git" directory).</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
To avoid having to deal with either an unwieldly 12GB repository or RSA-only blocklists, I'm considering creating another repository that would hold blocklists in a more focused format. Perhaps SHA-256(Modulus) for RSA keys, and SHA-256(X_Coordinate) for EC
keys?</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div class="elementToProof" style="direction: ltr;">I would prefer to reference the raw keys in the BRs and allow CAs the flexibility to determine the format they want to use in their checks.</div>
<div style="direction: ltr;"> </div>
<blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left: 1px solid rgb(204, 204, 204);">
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Finally, I'm open to transferring control of the whole <a href="https://github.com/CVE-2008-0166" id="OWAd29d834d-e60e-a3b7-25ca-22acafebe740" class="OWAAutoLink" shash="eBXjTmTYB1T3VDl+gSeZuk9nzaHz/v4+12qIKjZqulACkq20KVtr4MNG4/jWB02J2IZFPkYeB+A2pcKL4DKaklbJDxqlMxqaUJ4f8f/P1i9+yYGxIln5dUMBmDO6XXflOzeilaLiShGs7sDEfnxka/2sqvC2NQ66EE3XrhRGn2w=" originalsrc="https://github.com/CVE-2008-0166" data-auth="Verified" data-loopstyle="linkonly">
https://github.com/CVE-2008-0166</a> GitHub organization to CABForum, if that might be considered a suitable alternative to "import"ing one or more of the repositories into
<a href="https://github.com/cabforum" id="OWAa3a5c680-2aee-f83e-d245-b9761f7f6971" class="OWAAutoLink" shash="TQT8Yy2iFrosE/y1FM51jLn6YwUOzpVZh5RjNodnMUQNsysMz2j8peNgutofTTJOpzQCfZN6OM0X7B4ap6h4jdLGJAI0dNFtk5MZZx9gRVzNyllzhINS6p/+w4U0aRpsGt/G2IvbKJclD3CrcZ/tNrTz2Iix+sHQWQMvh01tkts=" originalsrc="https://github.com/cabforum" data-auth="Verified" data-loopstyle="linkonly">
https://github.com/cabforum</a>.</div>
</blockquote>
<div style="direction: ltr;"><br>
</div>
<div class="elementToProof" style="direction: ltr;">I'm not opposed, but I am concerned that this might further delay the ballot. If others prefer this approach, please speak up.</div>
<div style="direction: ltr;"><br>
</div>
<div style="direction: ltr;">- Wayne</div>
</body>
</html>