Re: Exposing TLS & Certificate Information in Javascript

Indeed... "/Secondary API Features/ that may be in scope are: control of 
TLS session login/logout, derivation of keys from TLS sessions, a 
simplified data protection function, multiple key containers, key 
import/export, a common method for accessing and defining properties of 
keys, and the lifecycle control of credentials such enrollment, 
selection, and revocation of credentials with a focus enabling the 
selection of certificates for signing and encryption."

So it's not there.

Le 04/03/2014 18:53, Ryan Sleevi a écrit :
>
> It was never in the spec. They are in the charter.
>
> On Mar 4, 2014 9:50 AM, "Aymeric Vitte" <vitteaymeric@gmail.com 
> <mailto:vitteaymeric@gmail.com>> wrote:
>
>
>     Le 04/03/2014 08:27, Ryan Sleevi a écrit :
>
>         Someone who is motivated for this can always write up a spec
>         proposal and see if the WG feels it is in charter (I believe
>         it may be listed under secondary features - ones we've agreed
>         to table for now) and whether such a spec is something the WG
>         should adopt. If someone wants to put forward a spec that can
>         actually address the issues rather than sleigh-of-hand them
>         away, it might be interesting to discuss - but I don't believe
>         such a thing is possible.
>
>
>     I think it was removed from secondary features but since it is
>     resurfacing periodically it should be there, but btw where are the
>     secondary features? I don't see any reference in the editor draft
>     neither links to a latest version.
>
>     Regards
>
>     Aymeric
>
>     -- 
>     Peersm : http://www.peersm.com
>     node-Tor : https://www.github.com/Ayms/node-Tor
>     GitHub : https://www.github.com/Ayms
>

-- 
Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms