doc update

diff --git a/doc/cha-gtls-app.texi b/doc/cha-gtls-app.texi
index 7e82a42ed19b52c89f329537514a23a2cae18b37..3e84ba2cb02713911e964846108b798d99c235df 100644 (file)
--- a/doc/cha-gtls-app.texi
+++ b/doc/cha-gtls-app.texi
@@ -982,7 +982,9 @@ renegotiation thus this option must be used with care.
 @item %STATELESS_COMPRESSION @tab
 will disable keeping state across records when compressing. This may
 help to mitigate attacks when compression is used but an attacker
-is in control of input data.
+is in control of input data. This has to be used only when the
+data that are possibly controlled by an attacker are placed in
+separate records.
 
 @item %SERVER_PRECEDENCE @tab
 The ciphersuite will be selected according to server priorities

diff --git a/doc/cha-intro-tls.texi b/doc/cha-intro-tls.texi
index 8279fff531e92266486535f2fd0521e1c6b23ef5..581a52777cb76afab329d6df09a4c2b11bbe255a 100644 (file)
--- a/doc/cha-intro-tls.texi
+++ b/doc/cha-intro-tls.texi
@@ -191,7 +191,9 @@ on @xcite{RFC3749}. The supported algorithms are shown below.
 Note that compression enables attacks such as traffic analysis, or even
 plaintext recovery under certain circumstances. To avoid some of these
 attacks GnuTLS allows each record to be compressed independently (i.e.,
-stateless compression), by using the "%STATELESS_COMPRESSION" priority string.
+stateless compression), by using the "%STATELESS_COMPRESSION" priority string,
+in order to be used in cases where the attacker controlled data are
+pt in separate records.
 
 @node Weaknesses and countermeasures
 @subsection Weaknesses and countermeasures