Re: [NNTP] New draft for COMPRESS (-01)
Julien ÉLIE <[email protected]> Sun, 31 Jan 2010 19:13:49 +0100
| Newsgroups | gmane.ietf.nntp |
|---|---|
| Organization | TrigoFACILE -- http://www.trigofacile.com/ |
| Message-ID | <84DB1794E573432A988ED170C31974F6@Iulius> |
Hi Ken,
> A server MUST NOT return the COMPRESS or
> STARTTLS capability labels in response to a CAPABILITIES command
> received after a compression layer is active, and a server MUST reply
> with a 502 response code if a syntactically valid COMPRESS or
> STARTTLS command is received while a compression layer is already
> active.
I think it is too strong and that STARTTLS may be returned by a server
that knows it can negotiate a TLS layer without compression.
See for instance in OpenSSL 1.0.0 (yes, the new upcoming version):
*) New option SSL_OP_NO_COMP to disable use of compression selectively
in SSL structures. New SSL ctrl to set maximum send fragment size.
Save memory by seeting the I/O buffer sizes dynamically instead of
using the maximum available value.
[Steve Henson]
So a news server can decide to return STARTTLS if SSL_OP_NO_COMP
is available. Otherwise, it does not return it after a successful
use of COMPRESS.
--=20
Julien =C9LIE
=AB En fait, je n'ai qu'une pr=E9tention, c'est de ne pas
plaire =E0 tout le monde. Plaire =E0 tout le monde, c'est plaire
=E0 n'importe qui. =BB (Sacha Guitry)=20