<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 23, 2017, at 8:09 PM, Ryan Sleevi via Public <<a href="mailto:public@cabforum.org" class="">public@cabforum.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Feb 23, 2017 at 7:54 PM, Phillip Hallam-Baker <span dir="ltr" class=""><<a href="mailto:philliph@comodo.com" target="_blank" class="">philliph@comodo.com</a>></span> wrote:<div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">SHA-2 is a direct swap for SHA-3 however. All that is required is to define the necessary OIDs. And the CURDLE charter does not preclude SHA-3, it merely does not list them as current work items.</div></div></blockquote><div class=""><br class=""></div><div class="">If you believe it's "just OIDs", then why hasn't Comodo made any proposals, given <a href="http://csrc.nist.gov/groups/ST/crypto_apps_infra/csor/algorithms.html" class="">http://csrc.nist.gov/groups/ST/crypto_apps_infra/csor/algorithms.html</a> ? Were you simply unaware of the OID assignment? Or is your assertion that such an OID as "id-rsassa-pkcs1-v1_5-with-sha3-256" ( { sigAlgs 13 } ) is insufficient? </div><div class=""><br class=""></div><div class="">I'm not sure how to interpret the rest of your reply, so I've omitted it, but I'm still curious about whether there are "any HSM vendors that CAs might use to ensure that their private keys are appropriately protected when generating these signatures?"</div><div class=""><br class=""></div><div class="">Doesn't this seem key to understanding how such certificates might exist, with respect to key protection, which is necessary and critical for user agents and cryptographic libraries to feel confident that supporting such certificates does not introduce undue risk to their users?</div></div></div></div></div></blockquote></div><br class=""><div class="">Ryan,</div><div class=""><br class=""></div><div class="">I wasn’t aware that NIST had allocated identifiers for RSA using PKCS#1 v1.5 over SHA3 hashes. Given that this exists, that strikes out that issue.</div><div class=""><br class=""></div><div class="">There are a number of HSMs out there suitable for key protection for this case already — almost every HSM I know about implements the <span style="font-family: Arial, sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;" class="">CKM_RSA_PKCS mechanism which allows signing arbitrary data. It doesn’t care if it is a SHA-1, SHA-256, or SHA3-256 hash.</span></div><div class=""><span style="font-family: Arial, sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;" class=""><br class=""></span></div><div class=""><span style="font-family: Arial, sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;" class="">All that is preventing the use of </span><span style="font-family: arial, helvetica, san-serif; font-size: small; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class="">id-rsassa-pkcs1-v1_5-with-sha3-256, </span><span style="font-family: arial, helvetica, san-serif; font-size: small; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class="">id-rsassa-pkcs1-v1_5-with-sha3-384, and </span><span style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><font face="arial, helvetica, san-serif" size="2" class="">id-rsassa-pkcs1-v1_5-with-sha3-512 is (1) the BRs and (2) lack of implantation by browsers. When is Chrome planning to support these algorithms?</font></span></div><div class=""><span style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><font face="arial, helvetica, san-serif" size="2" class=""><br class=""></font></span></div><div class=""><span style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><font face="arial, helvetica, san-serif" size="2" class="">Thanks,</font></span></div><div class=""><span style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><font face="arial, helvetica, san-serif" size="2" class="">Peter</font></span></div></body></html>