Dropping WHATWG, they do not really work with crypto, they just "inherited" something they will probably regret :--)
Kyle wrote: >Besides, insisting that the >browser itself hold the keys is counterproductive. That's not how <keygen> is implemented in FireFox AFAICT. Unfortunately this part is also non-trivial. If you look at Microsoft- solutions you typically have to select from a list of cryptographic service providers which is total BS for consumers. Here we need a standard where the issuer has a way signaling that it wants to use a particular container type. Ideas are welcome since this (of course) is a part of KeyGen2. Anders -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
