public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Huang Pei <huangpei@loongson.cn>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] encrypt.3: encrypt/encrypt_r, not crypt/crypt_r were deleted from 2.28
Date: Fri, 31 Dec 2021 12:39:02 +0100	[thread overview]
Message-ID: <2bcd174a-a08a-af32-ce72-12b9e46fb396@gmail.com> (raw)
In-Reply-To: <20211230094251.538-1-huangpei@loongson.cn>

Hi Huang,

On 12/30/21 10:42, Huang Pei wrote:
> See sysdeps/unix/sysv/linux/riscv/rv{32,64}/libcrypt.abilist from
> glibc
> 
> Signed-off-by: Huang Pei <huangpei@loongson.cn>

You're right, it seems:

alx@ady1:~/src/gnu/glibc$ git checkout glibc-2.28
Previous HEAD position was 23158b08a0 Update for 2.27 release
HEAD is now at 3c03baca37 Update NEWS, version.h, and features.h for 
glibc 2.28.
alx@ady1:~/src/gnu/glibc$
alx@ady1:~/src/gnu/glibc$ grep_glibc_prototype crypt
crypt/crypt.h:36:
extern char *crypt (const char *__phrase, const char *__salt)
      __THROW __nonnull ((1, 2));
posix/unistd.h:1124:
extern char *crypt (const char *__key, const char *__salt)
      __THROW __nonnull ((1, 2));
alx@ady1:~/src/gnu/glibc$
alx@ady1:~/src/gnu/glibc$ grep_glibc_prototype encrypt
alx@ady1:~/src/gnu/glibc$
alx@ady1:~/src/gnu/glibc$ git checkout glibc-2.27
Previous HEAD position was 3c03baca37 Update NEWS, version.h, and 
features.h for glibc 2.28.
HEAD is now at 23158b08a0 Update for 2.27 release
alx@ady1:~/src/gnu/glibc$
alx@ady1:~/src/gnu/glibc$ grep_glibc_prototype crypt
crypt/crypt.h:32:
extern char *crypt (const char *__key, const char *__salt)
      __THROW __nonnull ((1, 2));
posix/unistd.h:1126:
extern char *crypt (const char *__key, const char *__salt)
      __THROW __nonnull ((1, 2));
alx@ady1:~/src/gnu/glibc$
alx@ady1:~/src/gnu/glibc$ grep_glibc_prototype encrypt
crypt/crypt.h:40:
extern void encrypt (char *__glibc_block, int __edflag)
      __THROW __nonnull ((1));
posix/unistd.h:1131:
extern void encrypt (char *__glibc_block, int __edflag)
      __THROW __nonnull ((1));
alx@ady1:~/src/gnu/glibc$


I applied the patch to my tree.

Thanks,

Alex

> ---
>   man3/encrypt.3 | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/man3/encrypt.3 b/man3/encrypt.3
> index b4be7f3e0..b7df15777 100644
> --- a/man3/encrypt.3
> +++ b/man3/encrypt.3
> @@ -124,8 +124,8 @@ The function is not provided.
>   .SH VERSIONS
>   Because they employ the DES block cipher,
>   which is no longer considered secure,
> -.BR crypt (),
> -.BR crypt_r (),
> +.BR encrypt (),
> +.BR encrypt_r (),
>   .BR setkey (),
>   and
>   .BR setkey_r ()

-- 
Alejandro Colomar
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      reply	other threads:[~2021-12-31 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30  9:42 [PATCH] encrypt.3: encrypt/encrypt_r, not crypt/crypt_r were deleted from 2.28 Huang Pei
2021-12-31 11:39 ` Alejandro Colomar (man-pages) [this message]

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=2bcd174a-a08a-af32-ce72-12b9e46fb396@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=huangpei@loongson.cn \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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