All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx+linux-man@kernel.org>
To: Rich Felker <dalias@libc.org>
Cc: Alejandro Colomar <alx@kernel.org>,
	 Vincent Lefevre <vincent@vinc17.net>,
	linux-man@vger.kernel.org, libc-alpha@sourceware.org,
	 Walter Harms <wharms@bfs.de>,
	~hallyn/shadow@lists.sr.ht, musl@lists.openwall.com
Subject: Re: [musl] Re: [PATCH v1] man/man3/crypt.3: These functions accept many algorithms, not only DES
Date: Thu, 12 Nov 2026 13:27:13 +0100	[thread overview]
Message-ID: <avWwXGpq1OLtNDSV@devuan> (raw)
In-Reply-To: <20261112120831.GH5716@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

Hi Rich,

> Date: 2026-11-12 07:08:32-0500
> From: Rich Felker <dalias@libc.org>
>
[...]
> > 	+.SH VERSIONS
> > 	+While POSIX only specifies the DES algorithms for these functions,
> > 	+all systems implement several other algorithms.
> 
> POSIX doesn't specify any algorithm. It specifies the input format for
> salt in a way that's aligned with the traditional DES password hashing
> algorithm but it doesn't assign any actual definition for the
> algorithm.
> 
> DES hash provides the implementation-defined algorithm POSIX mandates
> exists but doesn't specify. The other hashes fill in the gaps where
> the specification leaves things undefined.
> 
> For practical purposes POSIX is irrelevant to the way you choose salt
> strings for producing new password hashes; it only specifies how to
> call the function and validate a password against a hash.

How about something this (we can improve the wording)?

	diff --git i/man/man3/crypt.3 w/man/man3/crypt.3
	index 524781d3c2a0..d579bc5394fb 100644
	--- i/man/man3/crypt.3
	+++ w/man/man3/crypt.3
	@@ -111,6 +111,9 @@ .SH ATTRIBUTES
	 .BR crypt_r ()
	 T}     Thread safety   MT-Safe
	 .TE
	+.SH VERSIONS
	+POSIX specifies a quite useless API,
	+and all systems extend it significantly.
	 .SH STANDARDS
	 .TP
	 .BR crypt ()


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-11-12 12:27 UTC|newest]

Thread overview: 29+ 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
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 [this message]
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
2026-11-12 14:58                             ` Alejandro Colomar
2026-11-12 18:08                               ` Rich Felker
2026-11-12 22:22                                 ` Alejandro Colomar

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=avWwXGpq1OLtNDSV@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=vincent@vinc17.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.