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:
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
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 nel...@bolyard.me wrote:
ksreedha...@gmail.com wrote, On 2009-04-01 17:54:
Hello,
I am [using] Mozilla-JSS as the provider in my Java
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 hostname -p port -d your nss cert db dir -v -2 -3 -c v
If you want full client auth
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,
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 hostname -p port -d your nss cert db dir -v -2 -3 -c
v. It fails with the error certificate issuer is not recognized.
If I use
6 matches
Mail list logo
