X-Git-Url: http://git.tuebingen.mpg.de/?a=blobdiff_plain;f=web%2Fmanual.m4;h=f7071167a62067a9dfbf0c4d594ed49d59a33f0e;hb=de8f6f12fdd4e740d10a167a839e37e79257e955;hp=2af59f5376b4ecfadc6ce12a38b5781698b276ce;hpb=6974e18e86064f870ff1c130b11ececc3e261158;p=paraslash.git

diff --git a/web/manual.m4 b/web/manual.m4
index 2af59f53..f7071167 100644
--- a/web/manual.m4
+++ b/web/manual.m4
@@ -202,9 +202,10 @@ In any case you'll need
 
 	git clone git://git.tuebingen.mpg.de/osl
 
-	- XREFERENCE(ftp://ftp.gnu.org/pub/gnu/gcc, gcc). The
-	EMPH(gnu compiler collection) is usually shipped with the
-	distro. gcc-3.3 or newer is required.
+	- XREFERENCE(ftp://ftp.gnu.org/pub/gnu/gcc, gcc) or
+	XREFERENCE(http://clang.llvm.org, clang). All gcc versions
+	>= 3.3 are currently supported. Clang version 1.1 or newer
+	should work as well.
 
 	- XREFERENCE(ftp://ftp.gnu.org/pub/gnu/make, gnu make) is
 	also shipped with the disto. On BSD systems the gnu make
@@ -214,11 +215,13 @@ In any case you'll need
 	scripts which run during compilation require the EMPH(Bourne
 	again shell).  It is most likely already installed.
 
-	- XREFERENCE(http://www.openssl.org/, openssl). The EMPH(Secure
-	Sockets Layer) library is needed for cryptographic routines
-	on both the server and the client side. It is usually shipped
-	with the distro, but you might have to install the "development
-	package" (called libssl-dev on debian systems) as well.
+	- XREFERENCE(http://www.openssl.org/, openssl) or
+	XREFERENCE(ftp://ftp.gnupg.org/gcrypt/libgcrypt/, libgcrypt).
+	At least one of these two libraries is needed as the backend
+	for cryptographic routines on both the server and the client
+	side. Both openssl and libgcrypt are usually shipped with the
+	distro, but you might have to install the development package
+	(libssl-dev or libgcrypt-dev on debian systems) as well.
 
 	- XREFERENCE(ftp://ftp.gnu.org/pub/gnu/help2man, help2man)
 	is used to create the man pages.
@@ -526,10 +529,10 @@ as follows:
 	this point on the communication is encrypted using the RC4
 	stream cipher with the session key known to both peers.
 
-paraslash relies on the quality of openssl's cryptographically strong
-pseudo-random bytes, on the security of the implementation of the
-openssl RSA and RC4 crypto routines and on the infeasibility to invert
-the SHA1 function.
+paraslash relies on the quality of the pseudo-random bytes provided
+by the crypto library (openssl or libgcrypt), on the security of
+the implementation of the RSA and RC4 crypto routines and on the
+infeasibility to invert the SHA1 function.
 
 Neither para_server or para_client create RSA keys on their own. This
 has to be done once for each user as sketched in REFERENCE(Quick start,