Rob Crittenden wrote:
Nelson B wrote:
Rob Crittenden wrote:
In an SSL client I want to force the SSL handshake to take place instead
of passively waiting for it to happen during the first write.
Here are a few (?) questions and comments:
1. Is this a blocking socket, or non-blocking?
Kyle Hamilton wrote:
On 11/2/06, Rob Crittenden [EMAIL PROTECTED] wrote:
It would be a whole lot simpler if I didn't want to force the handshake.
Indeed, that is how I initially wrote it, but then I changed my mind and
wrenched the code until it worked the way I wanted.
The problem being,
[Important note: this discussion is taking place in
mozilla.dev.security; please respect the Followup-To: header.]
For some time, the Mozilla Foundation has been taking part in a group
called the CA/Browser Forum (CABF), an association of the major
public-facing CAs and all the major
Nelson B wrote:
Rob Crittenden wrote:
In an SSL client I want to force the SSL handshake to take place instead
of passively waiting for it to happen during the first write.
Right after I connect to the server I'm currently doing this:
SSL_ResetHandshake(ssl, /* asServer */ PR_FALSE);
Rob Crittenden wrote:
One change I've made from tstclnt is using PR_ConnectContinue() instead
of PR_GetConnectStatus() which is deprecated.
The socket is already connected by the time I start doing any NSS calls.
I'm getting a connected socket and pushing SSL on top of that (rather
than
Sorry for my lack of knowledge on this topic. I am asking here rather
than in the bug I need this information for because I hope it might be
helpful to others in my situation. I searched the old newsgroup and
this one for the information and nothing jumped out at me. If it's
elsewhere, feel
I attempt to access a web page that requires a client certificate. I get
prompted for which cert to use, I select it, and then I get a blank
page. I look at the page source, and nothing. This happens on several
pages with the same server. I don't get an error message or anything
What does
They usually indicate either a time-out on the server side, or some
form of application processing error on the web/application server.
Have you checked your server logs to see if there are any error
messages?
I'm assuming that you don't have the usual problems related to the
certificates:
David Stutzman wrote:
Sorry for my lack of knowledge on this topic. I am asking here rather
than in the bug I need this information for because I hope it might be
helpful to others in my situation. I searched the old newsgroup and
this one for the information and nothing jumped out at me.
David Stutzman wrote:
Sorry for my lack of knowledge on this topic. I am asking here rather
than in the bug I need this information for because I hope it might be
helpful to others in my situation. I searched the old newsgroup and
this one for the information and nothing jumped out at me.
10 matches
Mail list logo
