W3C home > Mailing lists > Public > public-html-comments@w3.org > May 2011

Incomplete Spec. Re: KeyGen - Strange element in HTML5

From: Anders Rundgren <anders.rundgren@telia.com>
Date: Fri, 13 May 2011 14:02:01 +0200
Message-ID: <4DCD1DB9.3020704@telia.com>
To: public-html-comments@w3.org
In addition not meeting banks' expectations, <keygen>
is also severely underspecified.  The installation of
the associated client-certificate is not a part of the
specification.  In Firefox it is just a MIME-type
which also means that there is no user feedback
either such as redirect to success or failure pages.



On 2011-05-09 22:26, Anders Rundgren wrote:
> On 2011-05-09 22:10, Ian Hickson wrote:
>> On Mon, 9 May 2011, Anders Rundgren wrote:
>>> KeyGen is still a part of the HTML5 draft in spite of:
>>> - Not supported by MSFT
>>> - Not supported by iPhone
>>> - Not support by Safari on Windows
>>> - Not supported by the smart card vendors who have entirely different SW for accomplishing on-line enrollment
>> It's supported because browsers have to support it (or ActiveX) to be 
>> compatible with the Web. Going forward, vendors interested in crypto 
>> should get together to specify a better API.
> I can't get it to work in Chrome even.  I'm not alone:
> https://support.comodo.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1352
> In addition, there are essentially no users of this function.
> All serious parties provide their own SW for this purpose.
> The vendors have no intention whatsoever getting together
> on crypto.  They all plot with secret replacements for KeyGen.
> This include Google as well.
> Anders
Received on Friday, 13 May 2011 12:01:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:27 UTC