> From: Jeffrey Altman <[EMAIL PROTECTED]>
>
> jaltman> As I mentioned to you earlier, the activation of the ZLIB code in
> jaltman> OpenSSL is providing a 200% increase in throughput on my DSL
> jaltman> connections when used to connect Kermit's Telnet client to your TLS
> jaltman> Telnetd. However, I am having large numbers of problems with the ZLIB
> jaltman> code. On Unix, if libssl was built without ZLIB and the application
> jaltman> was built with it, then you get a
>
> Uhmm, how did you get it to initiate compression? As you said
> earlier, there's no TLS compression algorithm defined anywhere, and
> there no real way to tell the other party that compression is going
> on, or?
Well, actually, compression is defined in the TLS RFC. But due to
patent issues no one ever defined a compression algorithm to use with
it. (at least I think it was a patent issue.)
In any case, according to the note, Eric Young implemented RLE and
ZLIB compression algorithms back in 0.8.? All you have to do is
define ZLIB and link to libz.a.
I'm slowly sorting things out. To initiate compression in an app make
the following call after SSL_library_init()
#ifdef ZLIB
COMP_METHOD * cm = COMP_zlib();
if (cm->type != NID_undef)
SSL_COMP_add_compression_method(cm->type, cm);
#endif /* ZLIB */
Put this in both the client and server and watch things fly. However,
there appears to be some issues with reference counts. So don't do
this if you plan to reuse the SSL_CTX for multiple connections.
Jeffrey Altman * Sr.Software Designer
The Kermit Project * Columbia University
612 West 115th St * New York, NY * 10025 * USA
http://www.kermit-project.org/ * [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
