No Compression Overlap Error
Dash Shendy
admin at dash.za.net
Sat May 28 07:12:41 CEST 2011
Looking at the RFCs for TLS Compression:
FROM RFC3749: http://www.ietf.org/rfc/rfc3749.txt
<---SNIP--->
2. Compression Methods
TLS [2] includes the following compression method structure in
sections 6.1 and 7.4.1.2 and Appendix sections A.4.1 and A.6:
enum { null(0), (255) } CompressionMethod;
which allows for later specification of up to 256 different
compression methods. This definition is updated to segregate the
range of allowable values into three zones:
1. Values from 0 (zero) through 63 decimal (0x3F) inclusive are
reserved for IETF Standards Track protocols.
2. Values from 64 decimal (0x40) through 223 decimal (0xDF) inclusive
are reserved for assignment for non-Standards Track methods.
3. Values from 224 decimal (0xE0) through 255 decimal (0xFF)
inclusive are reserved for private use.
Additional information describing the role of the IANA in the
allocation of compression method identifiers is described in Section
5.
In addition, this definition is updated to include assignment of an
identifier for the DEFLATE compression method:
enum { null(0), DEFLATE(1), (255) } CompressionMethod;
<---SNIP--->
Wonder why mod_gnutls would send the reserved for private use value of 255?
I have tried several priority strings, including +COMP-NULL to no avail:(
Any Ideas?
Regards,
Dash Shendy
More information about the Gnutls-help
mailing list