On Fri, Mar 7, 2008 at 9:42 PM, D3||||!$ <[EMAIL PROTECTED]> wrote: > Hi All, > > I used the selfserv-tstclnt pair as a model to build an SSL client- > server pair written in C: Initially I had been supplying the command > argument -o which caused any problems in the authentication procedure > to be overriden(by enabling the use of a bad certificate handler > callback). > > I had generated the certificates with the right attributes but the > ownBadCertHandler callback in tstclnt is returning > PR_IN_PROGRESS_ERROR (-5934L): "Operation is still in progress > (probably a non-blocking connect)". This obviously is not an issue > with the server certificate but rather, has something to do with the > socket configuration... I guess this is because the tstclnt has been > configured as a non-blocking socket and calling PR_Connect is likely > to return this.... > > Could somebody help me out with it since my SSL client-server is also > returning the same error...
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#7257 and see why the ss->authCertificate failed. In particular, see what function ss->authCertificate is. Is it SSL_AuthCertificate? 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. Wan-Teh _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
