> I don't know what's is wrong. I can only suggest that you set a > breakpoint in tstclnt > here:http://lxr.mozilla.org/security/source/security/nss/lib/ssl/ssl3con.c...
ssl3con.c is not a accessed directly by tstclnt. Maybe it is called internally by one of the included headers, but I'm not sure which ones...LXR also merely throws up a single link to the file without showing the files in which it is accessed... Could you tell me in which files it is accessed...??? > and see why the ss->authCertificate failed. In particular, see what > function ss->authCertificate is. Is it SSL_AuthCertificate? Yes,SSL_AuthCertificate is used for authentication in tstclnt. > If ss->authCertificate is some other function, does it set the error > code before returning SECFailure? If it doesn't set the error code, > then the error code will be whatever is left over from a previously > failed function, which would explain the PR_IN_PROGRESS_ERROR > error. Another thing, PR_IN_PROGRESS_ERROR error is thrown when tstclnt is configured in non-blocking mode. tstclnt throws up PR_NOT_CONNECTED_ERROR when it is configured in blocking mode(selfserv is in blocking mode in both the cases..) In the API written by me, it is PR_Connect which is returning the same results... So it has something to do with the socket configuration. _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
