Replace (X)Salsa20 with ChaCha20

[govpn.git] / doc / encless.texi

diff --git a/doc/encless.texi b/doc/encless.texi
index fd267c73be4a78ee592f426707eb38c43d65c2dd..9513d6ce67f5bd8b473b0a0cb44cabd478e3666f 100644 (file)
--- a/doc/encless.texi
+++ b/doc/encless.texi
@@ -1,11 +1,4 @@
 @node Encless
-@cindex Encryptionless
-@cindex Encryptionless mode
-@cindex Chaffing-and-Winnowing
-@cindex AONT
-@cindex All-Or-Nothing-Transformation
-@cindex OAEP
-@cindex SAEP+
 @subsection Encryptionless mode
 
 Some jurisdictions can force user to reveal his encryption keys. However
@@ -15,7 +8,7 @@ some countries forbids usage of encryption (but again not the
 authentication).
 
 GoVPN provides special encryptionless mode of operation. In this mode it
-replaces Salsa20 function used for confidentiality with rather
+replaces ChaCha20 function used for confidentiality with rather
 well-known @url{http://people.csail.mit.edu/rivest/chaffing-980701.txt,
 Chaffing-and-Winnowing} (CnW) technology. This is rather traffic and
 resource hungry algorithm, so we use it after
@@ -32,12 +25,5 @@ signature algorithms. No encryption and steganography involved.
 In this mode each outgoing packet became larger on 4128 bytes and
 @ref{Noise, noise} is forcefully enabled. So this is resource hungry mode!
 
-@strong{Beware}: by default packet serial numbers are still processed
-through the XTEA encryption. It is not required for confidentiality and
-security, but for randomizing some parts of the traffic to make it
-indistinguishable from the noise, for making it more DPI-proof. It
-safely can be disabled, turned off or maybe its keys even can be
-revealed without security and forward secrecy loss.
-
 See @code{govpn/cnw} and @code{govpn/aont} packages for details of AONT
 and chaffing operations.