[openssl-users] Find size of available data prior to ssl_read

counterpoint martin at black-sheep-research.com
Thu Dec 17 09:36:40 UTC 2015

Thanks to Michael and Kurt for explanatory comments.

Is there an available setting that gives the upper limit on the amount of
data that will be obtained by a single ssl_read()?

The data stream is SQL requests, and often these are quite small, but they
can run to megabytes. I need to malloc a buffer for the data. If it is too
small, that will impose extra processing overheads in the rest of the
system. If it is too large, it will impose memory wastage on the rest of the
system.  The system has an upper limit of 32 KB on the initial size of a
buffer for reading, but that is way above the typical SQL request.

So, accepting that I can't set the size precisely, if there is a limit for
SSL data reads that is significantly lower than 32 KB then that might be a
feasible fixed buffer size.  If that isn't possible, maybe it will have to
be a tunable configuration value.  Any comments?

View this message in context: http://openssl.6102.n7.nabble.com/Find-size-of-available-data-prior-to-ssl-read-tp61722p61733.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.

More information about the openssl-users mailing list