Note that license conflict wasn't the only reason: LZO compression is not standardized for TLS, and GnuTLS have just hi-jacked a private use compression id 0xF2 for it. Is there anyone out there that actually needs to use LZO in TLS? If so, it would be useful to describe the protocol in an IETF document. If that isn't done, I wouldn't recommend enabling LZO.
/Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]