Nic James Ferrier <[EMAIL PROTECTED]> writes:
> But I don't seem to be able to use importUserCertificate to import the
> base64 encoded version of the certificate as you imply:
>
> <html>
> <head>
> <script>
> //<!--
> var nickname = "openidcert";
> var cert = "MIIC4DCCAkkCAWQwDQYJKoZIhvc....";
> var forceBackup = false;
>
> function load_certificate() {
> try {
> var log = window.crypto.importUserCertificates(nickname, cert,
> forceBackup);
> alert(log);
> }
> catch (e) {
> alert("problem importing certificate");
> }
> }
>
> document.addEventListener("load", load_certificate, false);
> //-->
> </script>
> </head>
> <body>
> <h1>Certificate installed?</h1>
> </body>
> </html>
>
> The cert data here is just base64'd certificate data. Not CMMF.
>
> I'm not sure that you meant whether I could do that or not but it
> doesn't work and it doesn't return an error.
Correction. It does return an error.
I thought of a way of achieving what I want... I use a data url to
open the certificate data in a hidden iframe from the response
HTML. Hence I have a purely one shot process that should be quite fool
proof. Of course... if the user interrupts it then there's a
problem. But that's just normal POST only once stuff.
--
Nic Ferrier
http://www.tapsellferrier.co.uk for all your tapsell ferrier needs
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
