David Schwartz schrieb:
I have try this, but it fails, because the is no way to find out when
the write buffer BIO has data that must send. I have try it with the
callback function. But this will not work, because the function must be
static. And than I can not acces the network object form
Now it will work better.
The problem was to that all must be event trigger.
Thanks a lot. Next I must add some error handling:)
Frank
smime.p7s
Description: S/MIME Cryptographic Signature
Hello,
I'm writing a program which can be compiled either with SSL support or
without. In order to limit the amount of #ifdef'ing I have to put
throughout the rest of my program, I'm trying to wrap SSL_read and
SSL_write so they can be treated like read/write on a regular socket.
This is
Steve,
You need to put select(ready to read or write) inside each (BOTH
SSL_read() and SSL_write()) of your while loops at the beginning, and
then cycle on WANT_READ or WANT_WRITE for BOTH SSL_read() and
SSL_write() loops.
You're getting high utilization because you are not putting select
Hello,
You need to put select(ready to read or write) inside each (BOTH
SSL_read() and SSL_write()) of your while loops at the beginning, and
then cycle on WANT_READ or WANT_WRITE for BOTH SSL_read() and
SSL_write() loops.
You're getting high utilization because you are not putting
On Sat, Aug 19, 2006 at 10:27:52PM +0200, Marek Marcola wrote:
I'm not sure if this is good solution because this will give
you semi-blocking behaviour (we are only in non-blocking wrapper
and checking for read/write is done by select() in upper layer).
You're right; I don't want blocking
On Sat, Aug 19, 2006 at 05:44:35PM -0400, Steven Young wrote:
You're right; I don't want blocking behaviour. The non-SSL part
of the code solves this by select()ing on the readable file descriptors
and only calling read() when there is something to be read.
To give you an idea of what's
Hello,
You should change loop ending condition - this loop should end
when SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE occur because
this errors may be returned on non-blocking sockets on SSL_read()
and on SSL_write(). On normal use this will happen mostly where
re-handshake is going on
On Sat, Aug 19, 2006 at 11:58:27PM +0200, Marek Marcola wrote:
In this situation calling SSL_read() next time is enough
(SSL layer will continue to write its own data and after this
read real data) but this SSL_read() should be performed
when socket descriptor is ready for write now.
Hi
I'm a little unclear on how this should be implemented.. so if I call
SSL_read, get -1 back, and err = SSL_ERROR_WANT_READ, do I just call
SSL_read again?
No. That error is telling you that you need to wait until the socket is
(again) readable.
Because that's what I've been doing
Marek, that was good pointer i'll add that . Thanks !
From: Marek Marcola [EMAIL PROTECTED]
Reply-To: openssl-users@openssl.org
To: openssl-users@openssl.org
Subject: Re: 3DES Encryption / Decryption using the EVP api
Date: Fri, 18 Aug 2006 11:08:55 +0200
Hello,
I want to decrypt using 3DES
Hi,
I've got some code that seems to work, except when the server responds with a 'large' amount of data.
When the server sends 5000 bytes of data to the client ,the client was able to read it and
every thing goes fine.But when the server passes more than 5000 bytes of data to the client,the
--- Sendil kumar [EMAIL PROTECTED] wrote:
Hi,
I've got some code that seems to work, except when
the server responds with
a 'large' amount of data.
When the server sends 5000 bytes of data to the
client ,the client was able to read it and
every thing goes fine.But when the server
13 matches
Mail list logo
