Hello All!
I am currently in the process of trying to get openssl to work with
non-blocking sockets (pheww, what a pain in the butt!). I am trying to
create an ssl socket object
which a user could use like a normal socket object. I am using some
existing librarys that I have which already take care of low level socket
communication, and I am using a memory BIO to push/pull data from this lower
network layer into openssl. There is one other intresting thing about these
ssl socket objects in that they use call backs. This means that the caller
gets informed as pieces of data come in and go out on the socket.
Because I am building this on top of a naive network layer, I would like a
tight estimate on the number of bytes of encrypted traffic result from N
bytes of unencrypted traffic. Basically:
# of encrypted bytes = F(# of unencrypted bytes).
I understand that this probably depends on the cipher I am using, but any
info you have would really help!
One other problem, slightly different, but in the same vain:
When dealing with non-blocking ssl handshaking, various SSL apis will return
errors indicating that they want you to read or write content in the BIOs.
If there is content to be read, often this means we have to read content off
the socket for the handshaking. What is a good way to determine how many
bytes we need to read in order to faciliate the handshaking? Is there
another API I can call which will tell me, or should I just naivelly grab
another kilo byte or so? I don't like this, because my lower network layer
wants greater precision then guestimates.
-tim
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
