Thanks for replying. I have added securityCallbacks (i.e. functions like myAuthCertificate, myGetClientAuthData, etc. as in the file "mozilla\security\nss\cmd\SSLsample\client.c". I do have one doubt with the code in this file. This SSL client takes a lot of command line arguments (please see the following code snippet). I don't understands why do we need to provide the certificate's nick name and the password to the SSL client.
Can you please comment on this?
Thanks.
switch(optstate->option) {
case 'C' : cipherString = PL_strdup(optstate->value); break;
case 'c' : connections = PORT_Atoi(optstate->value); break;
case 'd' : certDir = PL_strdup(optstate->value); break;
case 'n' : certNickname = PL_strdup(optstate->value); break;
case 'p' : port = PORT_Atoi(optstate->value); break;
case 'w' : password = PL_strdup(optstate->value); break;
case '\0': hostName = PL_strdup(optstate->value); break;
default : Usage(progName);--
Regards,
Umesh.
"Christian Biesinger" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
Umesh Bywar wrote:I am able to do normal HTTP communication but I am not able to do so over HTTPS. The problem that I see here is that the handshake is not happening. I see the "Client Hello and Server Hello" messages in ethereal but the rest of the handshake is not taking place. Does anyone have any ideas about how to solve this problem?
Are you setting the securityCallbacks of the socket transport?
_______________________________________________
mozilla-crypto mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-crypto
_______________________________________________ mozilla-crypto mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-crypto
