[cabfpub] Proposal of a SHA-1 exception procedure

Andrew R. Whalley awhalley at google.com
Mon Jun 6 10:18:54 MST 2016


Greetings,

To make commenting easier, I've converted the doc to Markdown and put it on
Github:

https://github.com/awhalley/docs-for-comment/blob/master/SHA1RequestProcedure.MD

Pull requests most welcome.

I've incorporated the feedback from Eric about ensuring the list is CCed on
any response, and some typos he caught.

(For anybody who's looked at the PDF, the differences from that are minor
and shown here
<https://github.com/awhalley/docs-for-comment/compare/0d991867eea023b3d60e3485685ee341f2dc2668...ae0261cd723487f44cc6301f939fbc2350e5a381?name=ae0261cd723487f44cc6301f939fbc2350e5a381&short_path=74615fb#diff-74615fb5efdb17b5b1e612614841494b>
)

Cheers,

Andrew

On Fri, Jun 3, 2016 at 1:53 PM, Andrew R. Whalley <awhalley at google.com>
wrote:

> Greetings,
>
> At the face to face meeting in Bilbao we heard there's still a need for
> new SHA-1 certs from some sectors, most notably the payment industry, to
> avoid outages of critical systems with real world impact.  We discussed if
> there was a way we might balance these cases against the vitally
> important need to ensure the security and safety of the public PKI.
>
> Please take a look at the proposed procedure, attached.  It outlines a way
> for CAs to request an exceptional SHA-1 issuance, including details which
> would help with a risk management decision.  It's not a guaranty that any
> such issuance would be acceptable, but provides a more structured approach
> than what's already occurred this year, e.g. with worldpay.
>
> I look forward to comments.
>
> Cheers,
>
> Andrew
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://cabforum.org/pipermail/public/attachments/20160606/005e1627/attachment.html 


More information about the Public mailing list