<html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> While testing chrome, we discovered that (a) keygen would soon not be supported: <ul> <li><a class="moz-txt-link-freetext" href="https://groups.google.com/a/chromium.org/forum/#!topic/security-dev/pX5NbX0Xack">https://groups.google.com/a/chromium.org/forum/#!topic/security-dev/pX5NbX0Xack</a> </li> </ul> (b) although keygen is still supported, it has been disabled by default with a workaround provided to re-enable it: <ul> <li><a class="moz-txt-link-freetext" href="https://support.quovadisglobal.com/kb/a470/deprecation-of-keygen-tag-in-chrome-chromium-browsers.aspx">https://support.quovadisglobal.com/kb/a470/deprecation-of-keygen-tag-in-chrome-chromium-browsers.aspx</a></li> </ul> Please review the attached patch which supplies a warning message and instructions on how to re-enable keygen on Chrome browsers that support this: <ul> <li><a href="https://fedorahosted.org/pki/ticket/2323">PKI TRAC #2323 - Firefox Warning appears in EE page launched from within Chrome</a></li> </ul> Additionally, an attempt was made to identify the case when KeyGen would not be available on Firefox and Chrome. -- Matt </body> </html>