Hopefully we can get permission from CertCo to
use they code in openssl, or we can replace the CertCo code, so that
we can bundle it into the next openssl release.
CertCo contributed that code to the OpenSSL community for general use,
as part of the regular OpenSSL licensing terms. It was
Do you have the object identifers for this? Do you know of any sources
of info I can look at about this extension. I can't find any mention
of it in RFC 2560.
See section 4.4.6 of RFC 2560 and the last few lines of appendix b.
It is required in the root CA certs or will it
work with it
Alicia da Conceicao wrote:
My contacts at Netscape mentioned that a few CA'a like Versign have
issued new root CA certs that support the new OCSP (Online Cert Status
Protocol), specified in RFC 2560. He also mentioned that OCSP support
will not only be included in future Netscape
You can do this via the authority information access extension. The
format is undocumented but something like:
authorityInfoAccess= OCSP;URI:http//some.oscp.server/whatever/path
Dear Steve:
Do you have the object identifers for this? Do you know of any sources
of info I can look at about
CA certs to support OCSP?
You can do this via the authority information access extension. The
format is undocumented but something like:
authorityInfoAccess= OCSP;URI:http//some.oscp.server/whatever/path
Dear Steve:
Do you have the object identifers for this? Do you know
