Thanks for narrowing down the cause of the problem. I'm trying this
with a 1024-bit RSA key. As stated earlier, I've tried this both with a
self-signed certificate, and with a Netscape CMS(ver 4.5) issued "OCSP
Responder" certificate, without any difference in behavior. Any other
key specific sources of trouble? Would copying the (base64-encoded)
contents of the certificate help?
Thanks again.
Hari
Hrmm...I just tried here in our lab what you're trying to do (Firefox ocsp to a Tumbleweed responder) and Firefox is reporting an error for me too but it's at least a string:
"Error trying to validate certificate from <host> using OCSP - unauthorized response."
I've tried selecting both the actual OCSP signer's certificate and the CA's cert that issued the OCSP signing cert and I get the same result from Firefox. The responder, however, is replying with a "GOOD" response. I'm using Firefox 1.0.2 and I tried it against both a 4.7 and 4.8 Tumbleweed responder. Just for kicks I tried it against a CoreStreet VA as well and got the same error from Firefox.
Dave _______________________________________________ mozilla-crypto mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-crypto
