X-Git-Url: https://tinc-vpn.org/git/browse?p=tinc;a=blobdiff_plain;f=README;h=c88027bd04caf0a074d3d88fd1e29e3241166092;hp=ec532437a7c65ddf9a8236b35626e7239b4c66f5;hb=0c7e0210d900185d4c1a9ffd969dc2a26d9523a9;hpb=85d33e563a0e4ce5910c9ba3b34eba8fbb1cbd30

diff --git a/README b/README
index ec532437..c88027bd 100644
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
-This is the README file for tinc version 1.1pre9. Installation
+This is the README file for tinc version 1.1pre11. Installation
 instructions may be found in the INSTALL file.
 
-tinc is Copyright (C) 1998-2013 by:
+tinc is Copyright (C) 1998-2014 by:
 
 Ivo Timmermans,
 Guus Sliepen <guus@tinc-vpn.org>,
@@ -36,12 +36,11 @@ at your own risk.
 Compatibility
 -------------
 
-Version 1.1pre9 is compatible with 1.0pre8, 1.0 and later, but not with older
+Version 1.1pre11 is compatible with 1.0pre8, 1.0 and later, but not with older
 versions of tinc.
 
-When the ExperimentalProtocol option is used, which is the default since
-1.1pre8, tinc is still compatible with 1.0.X and 1.1pre9 itself, but not with
-any other 1.1preX version.
+When the ExperimentalProtocol option is used, tinc is still compatible with
+1.0.X and 1.1pre11 itself, but not with any other 1.1preX version.
 
 
 Requirements
@@ -51,7 +50,7 @@ In order to compile tinc, you will need a GNU C compiler environment. Please
 ensure you have the latest stable versions of all the required libraries:
 
 - OpenSSL (http://www.openssl.org/) version 1.0.0 or later, with support for
-  elliptic curve cryptography (ECC) enabeld.
+  elliptic curve cryptography (ECC) and Galois counter mode (GCM) enabled.
 
 The following libraries are used by default, but can be disabled if necessary:
 
@@ -73,8 +72,8 @@ be forwarded by intermediate nodes.
 
 By default, nodes authenticate each other using 2048 bit RSA (or 521 bit
 ECDSA*) keys. Traffic is encrypted using Blowfish in CBC mode (or AES-256 in
-CTR mode*), authenticated using HMAC-SHA1 (or HMAC-SHA-256*), and is protected
-against replay attacks.
+GCM mode*), authenticated using HMAC-SHA1 (or GCM*), and is protected against
+replay attacks.
 
 *) When using the ExperimentalProtocol option.