"Nelson B Bolyard" wrote [to the WHATWG list]:
>I think that the KEYGEN tag's attributes could be extended to accept all
>the arguments that can be passed to crypto.generateCRMFRequest, quite easily.
Yes, but the crypto.* functions could be extended to do things you would never
be able to do in
Anders Rundgren wrote:
> I believe Mozilla will regret support for 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.
If you have special n
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 more because it's simple, you can put
it in HTML templates and it doesn't need Javascript.
When/if a standar
Anders Rundgren wrote:
>
> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-April/019338.html
>
> 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 more because it's simple, yo
4 matches
Mail list logo
