Re: ZLIB support not ready for prime time

[Richard Levitte - VMS Whacker]

From: Jeffrey Altman <[EMAIL PROTECTED]>

jaltman> I'm slowly sorting things out.  To initiate compression in an app make
jaltman> the following call after SSL_library_init()
jaltman> 
jaltman> #ifdef ZLIB
jaltman>     COMP_METHOD * cm = COMP_zlib();
jaltman>     if (cm->type != NID_undef)
jaltman>         SSL_COMP_add_compression_method(cm->type, cm);
jaltman> #endif /* ZLIB */

There's one fault in that code.  The first argument to
SSL_COMP_add_compression_method() is supposed to be the TLS algorithm
number.  cm->type is the OpenSSL NID for said algorithm, and that's a
higly internal number that is not to be mixed with anything internal,
really.

Of course, since there isn't any algorithm number assigned to ZLIB for
TLS, the number you use is completely at your leasure :-).  Don't
count on the above code to work when such a number is assigned,
however... 

-- 
Richard Levitte   \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]