From: Justin Erenkrantz Date: Sun, 13 Nov 2005 05:38:43 +0000 (+0000) Subject: Update transformations. X-Git-Tag: 2.3.0~2792 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=515eb1640f37e0f419ba1bb43cdafa2600ede0df;p=thirdparty%2Fapache%2Fhttpd.git Update transformations. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@332898 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/man/htpasswd.1 b/docs/man/htpasswd.1 index 6ecfb52d6e0..b1f854163a1 100644 --- a/docs/man/htpasswd.1 +++ b/docs/man/htpasswd.1 @@ -19,7 +19,7 @@ .el .ne 3 .IP "\\$1" \\$2 .. -.TH "HTPASSWD" 1 "2003-11-25" "Apache HTTP Server" "htpasswd" +.TH "HTPASSWD" 1 "2005-11-13" "Apache HTTP Server" "htpasswd" .SH NAME htpasswd \- Manage user files for basic authentication @@ -133,6 +133,12 @@ Web password files such as those managed by htpasswd should \fInot\fR be within .PP The use of the -b option is discouraged, since when it is used the unencrypted password appears on the command line\&. +.PP +When using the crypt() algorithm, note that only the first 8 characters of the password are used to form the password\&. If the supplied password is longer, the extra characters will be silently discarded\&. + +.PP +The SHA encryption format does not use salting: for a given password, there is only one encrypted representation\&. The crypt() and MD5 formats permute the representation by prepending a random salt string, to make dictionary attacks against the passwords more difficult\&. + .SH "RESTRICTIONS" .PP diff --git a/docs/manual/mod/core.xml.de b/docs/manual/mod/core.xml.de index 1deefbcc19f..f386cc72d79 100644 --- a/docs/manual/mod/core.xml.de +++ b/docs/manual/mod/core.xml.de @@ -1,7 +1,7 @@ - + + +