Jehan wrote: > Remko Tronçon;6010 Wrote: >>> So jabber.org is bugged. >> Dave reminded me that it could make sense to disable compression after >> TLS, namely when TLS is doing compression itself (and it doesn't make >> sense to do compression twice). Not sure if this is the reason why >> ejabberd removes the feature, though (AFAIK, not many clients/servers >> have TLS compression enabled). It might not hurt to check. >> >> cheers, >> Remko > > Ok I see. As here tls is not mandatory on jabber.org, it can make sense > (if it was mandatory, it would not). When you use TLS, then you cannot > use the zlib compression anymore and maybe even it is useless if the TLS > implementation used in ejabberd has itself a compression feature. It is > a possibility. > I will see check this by making a bug report at Process One and keep > you informed of the result.
I think there may already be a bug report filed about this. I know we discovered some strange ejabberd behavior related to compression and TLS at jabber.org when we required the use of TLS back in October (you could get around the TLS requirement if you negotiated compression first, or something like that). Maybe it's time to hold another Secure Communications Week so we can do some more testing? ;-) Peter
