> Need some help here. I initialize a connection with the
> following chunk of
> code (error checking removed for simplicity):
[snip]
> I thought that this meant that 'ssl_bio' would be the
> decrypted side and
> 'bio_io' would be the encrypted side. However, I send encrypted data to
>
Looks like you've solved your problem. I just wanted to point out one
thing
though.
The ssl_bio is no side. Its ssl_read and ssl_write would produce plain
text
and encrypted text respectively.
The sides that you talk about are actually the the 2 BIOs in the BIO
pair.
These act as buffers for ssl
> Looks like you've solved your problem. I just wanted to point out one
> thing
> though.
>
> The ssl_bio is no side. Its ssl_read and ssl_write would produce plain
> text
> and encrypted text respectively.
Not so. BIO_read and BIO_write on ssl_bio allow me to get in and out
plaintext.
>
> Not so. BIO_read and BIO_write on ssl_bio allow me to get in and out
> plaintext.
>
> > The sides that you talk about are actually the the 2 BIOs in the BIO
> > pair.
> > These act as buffers for ssl_read/write.
>
> Yes, the two BIO interfaces are 'ssl_bio' and 'bio_io'. This l
On Thu, Sep 07, 2000 at 08:53:47PM -0700, David Schwartz wrote:
> It seems to be working now. It just seems that I need to keep churning the
> SSL engine more than once, even if both BIO_read functions return -1. Go
> figure.
During the SSL handshake (which always occurs when the connectio
