If all that was sent was the protocol data that the write was
waiting for to satisfy the ssl state machine, and no application data
was
sent, would SSL_read return the number of bytes actually read off the
socket
(which is just protocol data), or would it read that transparently and
return 0 indi
You're right -- the latter.
Another thing to think about is that at any time, the remote peer might
request a re-negotiation. During such time, the session key will be
re-established requiring a few round-trips during the DH process. This
will all be handled behind the scenes as you attempt to m
Right, but let's say I'm doing an SSL_write, and I get a WANT_READ error. I
then select on the socket until data is available for reading. I then call
SSL_read. If all that was sent was the protocol data that the write was
waiting for to satisfy the ssl state machine, and no application data was
A return result of 0 typically means the other side closed the
connection.
Here is the section from SSL_read's man page with regards to a 0 return:
0 The read operation was not successful. The reason may either
be a
clean shutdown due to a "close notify" alert sent by the
pe
First of all, I want to thank everyone for all the information, especially
David with his excellent explanations. I know this thread is getting long,
but I really think I'm getting it now :) Just a few more questions and
comments...
> > > There may not be any application data, but there should
Hi All
I installed Apache/1.3.33 (Unix) mod_perl/1.29 mod_ssl/2.8.22
OpenSSL/0.9.7d on Solaris
But when I try to browse it using https://my.website.com I am getting
the following error in the browser:
The connection to my.website.com has terminated unexpectedly. Some data
may hav
> > There may not be any application data, but there should
> > be data sent over the SSL connection.
> Protocol data? Like an ack for some previous data sent?
Well, remember no data at all can be sent until a key is negotiated. So
if
you immediately call SSL_write, it will be unab
> > Yes, I think I understand what you are saying. If I get a
> WANT_READ
> > from a call to SSL_write, that means I need to read some
> data before I
> > can send.
>
> Not quite, it means the OpenSSL engine must read some
> data (from the
> socket) before you can perform the 'write' l
Hi all,
I’m
writing
a study about design aspects for a cryptographic service provider (CSP)
at the
moment. So I read some documentation about CSP-11, about the Microsoft
Cryptographic API and a lot of others, but I didn’t find much general
information
about a CSP. Can somebody tell me if someth
> Yes, I think I understand what you are saying. If I get a
> WANT_READ from a
> call to SSL_write, that means I need to read some data before I can send.
Not quite, it means the OpenSSL engine must read some data (from the
socket) before you can perform the 'write' logical operation on
1. In openssl-0.9.7g\demos\sign\, type the following command:
cl sign.c -I..\..\inc32 ..\..\out32dll\libeay32.lib -MD
2. Copy out32dll\libeay32.dll to demos\sign\, then run sign.exe
On 4/17/05, hao chen <[EMAIL PROTECTED]> wrote:
> Hi Tiange,
>
> Could you please do me a favour of telling me y
11 matches
Mail list logo
