ksreedha...@gmail.com wrote, On 2009-04-02 21:54:
> Hello,
>
> NSS version 3.11.4
>
> If I use the tstclnt with self signed certificate on the server (with
> some name in Issuer/Subject common name for Certiificate)
>
> "tstclnt -h -p -d -v -2 -3 -c
> v". It fails with the error "certificate
Hello,
NSS version 3.11.4
If I use the tstclnt with self signed certificate on the server (with
some name in Issuer/Subject common name for Certiificate)
"tstclnt -h -p -d -v -2 -3 -c
v". It fails with the error "certificate issuer is not recognized".
If I use "CACert" for this common name,
Hello Glen,
I tried to look into the source of classes where these exceptions were
thrown.
One interesting thing I observed is, JSSCipherSpi expects Public Key
only in "WRAP_MODE". But JCE_RSACipher is calling it in "ENCRYPT_MODE"
in which JSS expects a secret key. Since the passed key not a secr
Thanks Glen. Yes it works with the default provider. tstclnt fails
with the error Issuer certificate is invalid.
When I used with option -o (Override bad server cert), it works fine.
The certificate wes used is a Self signed certificate. So, probably
tstclnt didn't like it.
One more thing is, Ope
hi,
can you successfully connect to your server using JSSE with it's
default provider? meaning
not using mozilla-JSS as the provider?
I know you have used ssltap can you use NSS tool tstclnt?
tstclnt -h -p -d -v -2 -3 -c v
If you want full client auth specify your cert nickname with -n
Thanks Nelson for the reply.
Jss version is 4.2.5
JRE version is 1.6
NSS vesion is 3.11.4
See my comments inline.
On Apr 1, 8:45 pm, Nelson B Bolyard wrote:
> ksreedha...@gmail.com wrote, On 2009-04-01 17:54:
>
> > Hello,
>
> > I am [using] Mozilla-JSS as the provider in my Java application whi
Nelson Bolyard wrote:
Benjamin Smedberg wrote, On 2009-03-31 08:35:
In the other cases, we should just fix the bug, which is (I think) why Neil
posted originally.
I wish him Godspeed in fixing (or even filing) those bugs.
I filed bugs 486404/5 yesterday, and have a possible patch f
Nelson Bolyard wrote:
If you have public redistributable header files that declare the MSVCRT memory
guards, please send a pointer to them. Thanks.
I can't actually find the documentation I originally read about it; this
is the nearest that I get from a search:
http://msdn.microsoft.com/e
8 matches
Mail list logo