summaryrefslogtreecommitdiffstats
path: root/docs/manual/programs/htdbm.html.en.utf8
diff options
context:
space:
mode:
authorJoe Orton <jorton@apache.org>2020-12-17 13:48:30 +0100
committerJoe Orton <jorton@apache.org>2020-12-17 13:48:30 +0100
commited3ad3922c4654616d02c50c5c63303792e8e299 (patch)
tree9916944e30667d2175c09ab5b22e0f1e4cda36b7 /docs/manual/programs/htdbm.html.en.utf8
parentTreat non-leaf certificates present in SSLProxyMachineCertificateFile (diff)
downloadapache2-ed3ad3922c4654616d02c50c5c63303792e8e299.tar.xz
apache2-ed3ad3922c4654616d02c50c5c63303792e8e299.zip
Regenerate. [skip ci]
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1884553 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/programs/htdbm.html.en.utf8')
-rw-r--r--docs/manual/programs/htdbm.html.en.utf824
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/manual/programs/htdbm.html.en.utf8 b/docs/manual/programs/htdbm.html.en.utf8
index 63e871ff54..6b8183ccee 100644
--- a/docs/manual/programs/htdbm.html.en.utf8
+++ b/docs/manual/programs/htdbm.html.en.utf8
@@ -155,27 +155,27 @@
cannot be combined with the <code>-c</code> option.</dd>
<dt><code>-m</code></dt>
- <dd>Use MD5 encryption for passwords. On Windows and Netware, this is
+ <dd>Use MD5 hashing for passwords. On Windows and Netware, this is
the default.</dd>
<dt><code>-B</code></dt>
- <dd>Use bcrypt encryption for passwords. This is currently considered to
+ <dd>Use bcrypt hashing for passwords. This is currently considered to
be very secure.</dd>
<dt><code>-C</code></dt>
<dd>This flag is only allowed in combination with <code>-B</code> (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).</dd>
<dt><code>-d</code></dt>
- <dd>Use <code>crypt()</code> encryption for passwords. The default on all
+ <dd>Use <code>crypt()</code> hashing for passwords. The default on all
platforms but Windows and Netware. Though possibly supported by
<code>htdbm</code> on all platforms, it is not supported by the
<code class="program"><a href="../programs/httpd.html">httpd</a></code> server on Windows and Netware.
This algorithm is <strong>insecure</strong> by today's standards.</dd>
<dt><code>-s</code></dt>
- <dd>Use SHA encryption for passwords. Facilitates migration from/to Netscape
+ <dd>Use SHA hashing for passwords. Facilitates migration from/to Netscape
servers using the LDAP Directory Interchange Format (ldif).
This algorithm is <strong>insecure</strong> by today's standards.</dd>
@@ -215,7 +215,7 @@
does exist, the password is changed.</dd>
<dt><code><var>password</var></code></dt>
- <dd>The plaintext password to be encrypted and stored in the DBM file.
+ <dd>The plaintext password to be hashed and stored in the DBM file.
Used only with the <code>-b</code> flag.</dd>
<dt><code>-T<var>DBTYPE</var></code></dt>
@@ -261,7 +261,7 @@
<p>Adds or modifies the password for user <code>jsmith</code>. 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 <code>crypt()</code> routine will be used. If the file does not
exist, <code>htdbm</code> will do nothing except return an error.</p>
@@ -302,14 +302,14 @@
not be fetchable with a browser.</p>
<p>The use of the <code>-b</code> option is discouraged, since when it is
- used the unencrypted password appears on the command line.</p>
+ used the plaintext password appears on the command line.</p>
<p>When using the <code>crypt()</code> 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.</p>
- <p>The SHA encryption format does not use salting: for a given password,
- there is only one encrypted representation. The <code>crypt()</code> and
+ <p>The SHA hashing option does not use salting: for a given password,
+ there is only one hashed representation. The <code>crypt()</code> and
MD5 formats permute the representation by prepending a random salt string,
to make dictionary attacks against the passwords more difficult.</p>
@@ -318,13 +318,13 @@
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="restrictions" id="restrictions">Restrictions</a> <a title="Permanent link" href="#restrictions" class="permalink">&para;</a></h2>
- <p>On the Windows platform, passwords encrypted with
+ <p>On the Windows platform, passwords hashed with
<code>htdbm</code> are limited to no more than <code>255</code>
characters in length. Longer passwords will be truncated to 255
characters.</p>
<p>The MD5 algorithm used by <code>htdbm</code> 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.</p>
<p>Usernames are limited to <code>255</code> bytes and may not include the