W3C home > Mailing lists > Public > public-hb-secure-services@w3.org > May 2016

Re: removing keygen from HTML

From: Erik Anderson <eanders@pobox.com>
Date: Tue, 31 May 2016 14:42:14 -0400
Message-Id: <1464720134.3747232.623933441.76F0FAE8@webmail.messagingengine.com>
To: public-hb-secure-services@w3.org
I dont know that "remove keygen from HTML." but instead delegate to
hardware if present.

Currently our approach is

1) If secure hardware is present, responsibility is delegated to the
hardware to generate the key
2) If hardware not present, do the old way and let the software create
and manage the key

Erik Anderson
Bloomberg

On Mon, May 30, 2016, at 05:54 AM, GALINDO Virginie wrote:
> Dear all,
> FYI, keyge n conversation starting again in the TAG mailing list.
> One of the use case we have our plate is the secure credential
> management.
> This has also something to do with the use case of key gen in the HTML
> specification.
> Regards,
> Virginie
> 
> 
> 
> -----Original Message-----
> From: Chaals McCathie Nevile [mailto:chaals@yandex-team.ru]
> Sent: lundi 30 mai 2016 11:40
> To: www-tag@w3.org
> Subject: removing keygen from HTML
> 
> Hi folks,
> 
> there is an open issue [1] and open call for consensus [2] to remove
> keygen from HTML. Since the TAG, or its members, appear to have opinions
> about our spec, we'd be grateful to hear them.
> 
> cheers
> 
> Chaals
> 
> [1] https://github.com/w3c/html/issues/43
> [2] http://www.w3.org/mid/op.yhs220oos7agh9@widsith.local
> 
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
>   chaals@yandex-team.ru - - - Find more at http://yandex.com
> 
> ________________________________
>  This message and any attachments are intended solely for the addressees
>  and may contain confidential information. Any unauthorized use or
>  disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable
> for the message if altered, changed or falsified. If you are not the
> intended recipient of this message, please delete it and notify the
> sender.
> Although all reasonable efforts have been made to keep this transmission
> free from viruses, the sender will not be liable for damages caused by a
> transmitted virus.
Received on Tuesday, 31 May 2016 19:35:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 31 May 2016 19:35:47 UTC