Re: SEC_ERROR_EXTENSION_NOT_FOUND

Nelson, Thank you for your response. The module is an access manager Apache agent module from Sun (libamapc2). This gets loaded when Apache starts and handles handles authentication of AM protected applications. You are correct that I don't see sec_error_ext_not_found in logs, but I found it

Re: SEC_ERROR_EXTENSION_NOT_FOUND

On Oct 13, 6:26 am, star_ni...@my-deja.com wrote: > Hello, > > We are getting this error from a library. I have been told the module > is configured trust all certs. Can someone shed some light on libssl, > libnss stack trace and the error? > > Thanks > SN I apologize I missed the trace

SEC_ERROR_EXTENSION_NOT_FOUND

Hello, We are getting this error from a library. I have been told the module is configured trust all certs. Can someone shed some light on libssl, libnss stack trace and the error? Thanks SN -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev

Re: couple of certifcate usage questions

Nelson, Thank you, that did clarify a lot. One follow-on question... Does the trust flags always override certificate type and extensions? For instance, if a certificate did not have the "basic constraint" extension needed for CA certifcate and if that certifcate's trust were modified to be a

couple of certifcate usage questions

Hi, Sorry if this has already been answered, I searched for an answer before asking. 1. What should be trust args for a self-signed certifcate, that needs to be used as a server cert? Should that be valid peer or trusted peer? Can self-signed cert be used with NSS for server authentication? 2. W