From: Alejandro Colomar <alx+linux-man@kernel.org>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Alejandro Colomar <alx@kernel.org>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org,
Walter Harms <wharms@bfs.de>, Rich Felker <dalias@libc.org>,
~hallyn/shadow@lists.sr.ht, musl@lists.openwall.com
Subject: Re: [PATCH v1] man/man3/crypt.3: These functions accept many algorithms, not only DES
Date: Wed, 11 Nov 2026 19:55:01 +0100 [thread overview]
Message-ID: <avS4ybx_EfRvGsw1@devuan> (raw)
In-Reply-To: <avSERDjw/CeqN60U@hallyn.com>
[-- Attachment #1: Type: text/plain, Size: 2576 bytes --]
Hi Serge,
> Date: 2026-11-11 09:05:40-0600
> From: "Serge E. Hallyn" <serge@hallyn.com>
>
[...]
> > - salt is a two‐character string chosen from the set
> > - [a-zA-Z0-9./]. This string is used to perturb the algo‐
> > - rithm in one of 4096 different ways.
> > -
> > - By taking the lowest 7 bits of each of the first eight
> > - characters of the key, a 56‐bit key is obtained. This
> > - 56‐bit key is used to encrypt repeatedly a constant string
> > - (usually a string consisting of all zeros). The returned
> > - value points to the hashed password, a series of 13 print‐
> > - able ASCII characters (the first two characters represent
> > - the salt itself). The return value points to static data
> > - whose content is overwritten by each call.
> > -
> > - Warning: the key space consists of 2**56 equal 7.2e16 pos‐
> > - sible values. Exhaustive searches of this key space are
> > - possible using massively parallel computers. Software,
> > - such as crack(1), is available which will search the por‐
> > - tion of this key space that is generally used by humans
> > - for passwords. Hence, password selection should, at mini‐
> > - mum, avoid common words and names. The use of a passwd(1)
> > - program that checks for crackable passwords during the se‐
> > - lection process is recommended.
> > -
> > - The DES algorithm itself has a few quirks which make the
> > - use of the crypt() interface a very poor choice for any‐
> > - thing other than password authentication. If you are
> > - planning on using the crypt() interface for a cryptography
> > - project, don’t do it: get a good book on encryption and
> > - one of the widely available DES libraries.
> > + salt is a string used for determining the hasing algorithm
>
> typo: hashing
Thanks! Fixed.
> > + (possibly including parameters). It is also used to per‐
> > + turb the algorithm.
BTW, I suspect the salt is not used for perturbing the algorithm
anymore. From musl's source code, at least for SHA-512, I _think_ it's
not reading past the third '$', and thus it's not reading any random-ish
bytes.
Should I drop the second sentence?
Have a lovely night!
Alex
> > +
> > + The returned value points to the hashed password. The re‐
> > + turn value points to static data whose content is over‐
> > + written by each call.
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-11-11 18:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 23:58 [PATCH v1] man/man3/crypt.3: These functions accept many algorithms, not only DES Alejandro Colomar
2026-11-10 0:01 ` Alejandro Colomar
2026-11-11 15:05 ` Serge E. Hallyn
2026-11-11 18:55 ` Alejandro Colomar [this message]
2026-11-11 21:13 ` [musl] " Rich Felker
2026-11-11 21:43 ` Alejandro Colomar
2026-11-12 1:52 ` Vincent Lefevre
2026-11-12 2:53 ` Rich Felker
2026-11-12 3:29 ` Vincent Lefevre
2026-11-12 3:37 ` [musl] " Rich Felker
2026-11-12 10:28 ` Alejandro Colomar
2026-11-12 11:40 ` Vincent Lefevre
2026-11-12 12:08 ` Alejandro Colomar
2026-11-12 13:15 ` Vincent Lefevre
2026-11-12 13:26 ` Alejandro Colomar
2026-11-12 12:08 ` Rich Felker
2026-11-12 12:27 ` Alejandro Colomar
2026-11-12 12:41 ` Szabolcs Nagy
2026-11-12 13:12 ` Alejandro Colomar
2026-11-12 13:27 ` Vincent Lefevre
2026-11-12 13:17 ` Vincent Lefevre
2026-11-12 13:23 ` Alejandro Colomar
2026-11-12 13:45 ` Vincent Lefevre
2026-11-12 13:55 ` Rich Felker
2026-11-12 14:07 ` Alejandro Colomar
2026-11-12 14:43 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=avS4ybx_EfRvGsw1@devuan \
--to=alx+linux-man@kernel.org \
--cc=alx@kernel.org \
--cc=dalias@libc.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=musl@lists.openwall.com \
--cc=serge@hallyn.com \
--cc=wharms@bfs.de \
--cc=~hallyn/shadow@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox