<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Bonjour,<br class="">
<div apple-content-edited="true" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
</div>
</div>
<div>
<blockquote type="cite" class="">
<div class="">Le 24 févr. 2016 à 20:31, Peter Bowen <<a href="mailto:pzb@amzn.com" class="">pzb@amzn.com</a>> a écrit :</div>
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Feb 24, 2016, at 11:07 AM, Ryan Sleevi <<a href="mailto:sleevi@google.com" class="">sleevi@google.com</a>> wrote:</div>
<div class="">
<p dir="ltr" class="">On Feb 24, 2016 10:56 AM, "Jeremy Rowley" <<a href="mailto:jeremy.rowley@digicert.com" class="">jeremy.rowley@digicert.com</a>> wrote:<br class="">
><br class="">
> I’ve been playing around with Peter Bowen’s certlint (an excellent tool) and, looking at the cert universe as a whole, there are some noticeable issues with the BRs and RFC 5280 that I though merited a public CAB Forum discussion. Some of this is likely
me not knowing the entire history of 5280, so I appreciated any explanation. If there’s exceptions we would like to make to RFC5280, we should probably also push a bis with IETF at the same time.<br class="">
><br class="">
</p>
<p dir="ltr" class="">> 3) Years ago, we discussed that 2047 bit certs were equivalent to 2048 bit certs (although the discussion may have occurred solely on the Mozilla mailing list). We should codify this exception.</p>
<p dir="ltr" class="">IMO, this is a giant hack that browsers did because CAs have trouble counting (see also: serial numbers), which itself is a statement that the underlying libraries played a very liberal definition.</p>
<p dir="ltr" class="">I would prefer not.</p>
<div class=""><br class="">
</div>
</div>
</blockquote>
<br class="">
</div>
I think there is a misunderstanding here. There has never been a requirement that the modulus contain a certain number of bits set to ‘1’. What is required is that the modulus be a 2048-bit number. The problem is that a 2048-bit number can have one or more
of the high order bits being zero. When calculating the modulus “size”, all an observer can do find the left-most bit set to ‘1’ and use that. RSA moduli normally are the product of two prime numbers. OpenSSL and some other generating tools have a function
that makes the top bit of each prime number to be 1 which ensures the result will have the top bit set to 1. However a random prime could be smaller, resulting in a smaller results.</div>
</div>
</blockquote>
<br class="">
</div>
<div>It’s like saying 998 is a 4 digits number whose highest-order digit is set to 0.</div>
<br class="">
<div class="">
<div class="">Cordialement,</div>
<div class="">Erwann Abalea</div>
</div>
<div class=""><br class="">
</div>
</body>
</html>