I think the buffering should be fine. SSL_shutdown doesn't appear to flush the
outgoing buffers (which is stupid IMO but whatever), but as long as you're in
blocking mode SSL_write will always send the data, and SSL_read will always
just return what it has so far, unless there is no data buffered. Since you
know exactly how big this struct is, it should never happen (except in the case
of a malicious client or server, which is something you might or might not care
about depending on various factors).
good to know.
how can i minimize the amount of excess/padding data sent across? and, does minimizing this padding make the enryption any less secure?
BTW, openssl-users is, at least based on message counts, more active.
thanks. would development-related questions like this be okay to ask there?
- philip
______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
