From 3161ed034bbea40a705303811d7213aff9be17d2 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 28 Apr 2024 01:56:20 +0200 Subject: Merging upstream version 2.4.59. Signed-off-by: Daniel Baumann --- docs/manual/programs/htdbm.html.en | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) (limited to 'docs/manual/programs/htdbm.html.en') diff --git a/docs/manual/programs/htdbm.html.en b/docs/manual/programs/htdbm.html.en index 00aa52d..5eb9e5c 100644 --- a/docs/manual/programs/htdbm.html.en +++ b/docs/manual/programs/htdbm.html.en @@ -155,27 +155,27 @@ cannot be combined with the -c option.
-m
-
Use MD5 encryption for passwords. On Windows and Netware, this is +
Use MD5 hashing for passwords. On Windows and Netware, this is the default.
-B
-
Use bcrypt encryption for passwords. This is currently considered to +
Use bcrypt hashing for passwords. This is currently considered to be very secure.
-C
This flag is only allowed in combination with -B (bcrypt - encryption). It sets the computing time used for the bcrypt algorithm + hashing). It sets the computing time used for the bcrypt algorithm (higher is more secure but slower, default: 5, valid: 4 to 31).
-d
-
Use crypt() encryption for passwords. The default on all +
Use crypt() hashing for passwords. The default on all platforms but Windows and Netware. Though possibly supported by htdbm on all platforms, it is not supported by the httpd server on Windows and Netware. This algorithm is insecure by today's standards.
-s
-
Use SHA encryption for passwords. Facilitates migration from/to Netscape +
Use SHA hashing for passwords. Facilitates migration from/to Netscape servers using the LDAP Directory Interchange Format (ldif). This algorithm is insecure by today's standards.
@@ -215,7 +215,7 @@ does exist, the password is changed.
password
-
The plaintext password to be encrypted and stored in the DBM file. +
The plaintext password to be hashed and stored in the DBM file. Used only with the -b flag.
-TDBTYPE
@@ -261,7 +261,7 @@

Adds or modifies the password for user jsmith. The user is prompted for the password. If executed on a Windows system, the password - will be encrypted using the modified Apache MD5 algorithm; otherwise, the + will be hashed using the modified Apache MD5 algorithm; otherwise, the system's crypt() routine will be used. If the file does not exist, htdbm will do nothing except return an error.

@@ -288,14 +288,14 @@ not be fetchable with a browser.

The use of the -b option is discouraged, since when it is - used the unencrypted password appears on the command line.

+ used the plaintext password appears on the command line.

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.

-

The SHA encryption format does not use salting: for a given password, - there is only one encrypted representation. The crypt() and +

The SHA hashing option does not use salting: for a given password, + there is only one hashed representation. The crypt() and MD5 formats permute the representation by prepending a random salt string, to make dictionary attacks against the passwords more difficult.

@@ -304,13 +304,13 @@
top

Restrictions

-

On the Windows platform, passwords encrypted with +

On the Windows platform, passwords hashed with htdbm are limited to no more than 255 characters in length. Longer passwords will be truncated to 255 characters.

The MD5 algorithm used by htdbm is specific to the Apache - software; passwords encrypted using it will not be usable with other Web + software; passwords hashed using it will not be usable with other Web servers.

Usernames are limited to 255 bytes and may not include the @@ -338,7 +338,7 @@ var comments_identifier = 'http://httpd.apache.org/docs/2.4/programs/htdbm.html' } })(window, document); //-->