From: cajus <cajus@594d385d-05f5-0310-b6e9-bd551577e9d8>
Date: Mon, 5 May 2008 15:44:42 +0000 (+0000)
Subject: Updated debian readme
X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=67856b82b502563fe78bf25ac0a5c664f307f4dc;p=gosa.git

Updated debian readme


git-svn-id: https://oss.gonicus.de/repositories/gosa/trunk@10769 594d385d-05f5-0310-b6e9-bd551577e9d8
---

diff --git a/gosa-core/debian/README.Debian b/gosa-core/debian/README.Debian
index cfb650690..f23c04c77 100644
--- a/gosa-core/debian/README.Debian
+++ b/gosa-core/debian/README.Debian
@@ -18,8 +18,14 @@ web applications (well, this is the rule for allmost every web application
 that stores information somewhere around) to read the gosa.conf file, which
 may contain vital information about your LDAP service.
 
-To make it harder to extract these passwords, they get passed by request
-headers by default.
+To make it harder to extract these passwords, they get encrypted by a
+master password only readable by the GOsa location.
+
+You can simply migrate old existing passwords by typing:
+
+# a2enmod headers
+# gosa-encrypt-passwords
+# /etc/init.d/apache2 reload
 
 If this is not enough for you (exploitable PHP code may make it possible to
 read the webservers memory), you can simply create another webserver instance