Michael Ströder wrote:
If I were to select between these to solutions, generateCRMFRequest would be my choice because protocols do not belong to HTML pages.
That's nonsense. I like <keygen> more because it's simple, you can put it in HTML templates and it doesn't need Javascript.
When/if a <keygen> standard becomes ready it may not be that simple anymore. I believe Mozilla will regret support for <keygen> standardization because few will like the quite delayed end-result since it still won't [*] support serious users of PKI who want to deal with policy as well. Policy means "container quality", PINs etc. For non-serious usage <keygen> is OK as it is :-) JavaScript is effectively the client-side programming language of the web making it rather pointless downplaying a JavaScript solution. Anders *] Because that's infeasible without introducing additional protocols rounds and then we have definitely left the HTML world. -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
