Re: NSS 3.12.5.0: Error '-8152' (SEC_ERROR_INVALID_KEY) when connecting to ssl-enabled servers

2012-05-08 Thread Nelson B Bolyard
On 2012/05/08 04:53 PDT, Bernhard Thalmayr wrote: > > Hi experts, an OpenAM community member is using OpenAM policy agent to > connect to an ssl-secured server. > > The policy agent uses NSPR 4.8.2, NSS 3.12.5.0 optimized build for Linux > (RHEL) 64bit. > > If the agent tries to open a connect

Re: Provide own CA

2012-05-08 Thread Marc Patermann
Hi, Wan-Teh Chang schrieb (07.05.2012 20:39 Uhr): On Mon, May 7, 2012 at 9:20 AM, Marc Patermann wrote: I posted my issue on Thunderbird-Enterprise before and Ludovic Hirlimann sent me here. I created an own CA and put the cert in cert8.db by GUI in Thunderbird 10 ESR. As far as I understan

NSS 3.12.5.0: Error '-8152' (SEC_ERROR_INVALID_KEY) when connecting to ssl-enabled servers

2012-05-08 Thread Bernhard Thalmayr
Hi experts, an OpenAM community member is using OpenAM policy agent to connect to an ssl-secured server. The policy agent uses NSPR 4.8.2, NSS 3.12.5.0 optimized build for Linux (RHEL) 64bit. If the agent tries to open a connection to a specific, ssl-enabled OpenAM server, error '-8152' is r

Re: To NSS-Java or not to NSS-Java, thats the question.

2012-05-08 Thread helpcrypto helpcrypto
> And what about applets without JSS, using Secmod [1] or the sunpkcs11 > [2] provider? > > [1] http://www.docjar.com/docs/api/sun/security/pkcs11/Secmod.html > [2] http://www.docjar.com/docs/api/sun/security/pkcs11/SunPKCS11.html Any comments? -- dev-tech-crypto mailing list dev-tech-crypto@lis