From: Alejandro Colomar <alx@kernel.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] crypt.3: The library is "libcrypt", not "libcrypto"
Date: Sun, 16 Jul 2023 03:37:06 +0200 [thread overview]
Message-ID: <5a875d64-331c-7c83-b6aa-0cf8a2b23a19@kernel.org> (raw)
In-Reply-To: <1855d0c68cbae144e6f5613ee4a6f109cd5e3562.camel@xry111.site>
[-- Attachment #1.1: Type: text/plain, Size: 1957 bytes --]
On 2023-07-16 03:18, Xi Ruoyao wrote:
> On Sun, 2023-07-16 at 02:59 +0200, Alejandro Colomar wrote:
>> Hi Xi!
>>
>> On 2023-07-15 20:41, Xi Ruoyao wrote:
>>> libcrypt is the password hashing library, and libcrypto is a
>>> completely
>>> different library (OpenSSL cryptography library).
>>
>> Thanks! My mistake.
>>
>>>
>>> Signed-off-by: Xi Ruoyao <xry111@xry111.site>
>>> ---
>>> man3/crypt.3 | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/man3/crypt.3 b/man3/crypt.3
>>> index 1f3e4792e..ad14cb4f7 100644
>>> --- a/man3/crypt.3
>>> +++ b/man3/crypt.3
>>> @@ -20,7 +20,7 @@
>>> crypt, crypt_r \- password and data encryption
>>> .SH LIBRARY
>>> Encryption and decryption library
>>
>> Is the above line accurate, or should we improve it?
>
> Hmm, I'm not sure.
>
> This library is only a password hashing library today (and also in UNIX
> 6 :), but when it provided encrypt() function (from UNIX 7 to Glibc
> 2.27) it can really do "encryption and decryption" (in a broken way
> though).
Thanks!
I prefer to be on the safe side when it's about crypto stuff. Calling
it an encryption library when it should be considered as such, and it's
unsafe as such, is hurting our readers. I prefer to call it "Hashing
library", after your response. Feel free to send a patch, or tell me
if you're busy and I'll prepare this one.
>
> But I guess we can change "password and data encryption" to "password
> hashing", at least.
Agree. Please send a patch, or ask me to do it myself.
Thanks again!
Alex
>
>>> -.RI ( libcrypto ", " \-lcrypto )
>>> +.RI ( libcrypt ", " \-lcrypt )
>>
>> I see that another page probably also needs to be fixed.
>> Would you mind fixing it too,if appropriate, in this patch?
>
> Ah indeed, I didn't catch it.
>
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-16 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 18:41 [PATCH] crypt.3: The library is "libcrypt", not "libcrypto" Xi Ruoyao
2023-07-16 0:59 ` Alejandro Colomar
2023-07-16 1:18 ` Xi Ruoyao
2023-07-16 1:37 ` Alejandro Colomar [this message]
2023-07-16 1:56 ` Xi Ruoyao
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=5a875d64-331c-7c83-b6aa-0cf8a2b23a19@kernel.org \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=xry111@xry111.site \
/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