Has anyone else had need to reduce TLS session memory footprint? When acting as server (Apache 2.0 running on Linux), I measure 57kB used after https session established, with peak memory use at 99kB (during establishment). A s_server/s_client TLS session shows slightly higher values.
./ssl/ssl3.h defines SSL3_RT_MAX_PLAIN_LENGTH as 16384. This #define is the basis of quite a few relatively large mallocs. Is 16384 a sacred number? What are the implications of reducing the value to 2048 or 4096? Would the change have any effect on functionality, stability, and/or performance?
Thanks,
Randy Sales
[EMAIL PROTECTED]
