public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Zack Weinberg" <zack@owlfolio.org>
To: "Adhemerval Zanella" <adhemerval.zanella@linaro.org>,
	"GNU libc development" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2 2/2] crypt: Remove libcrypt support
Date: Mon, 02 Oct 2023 10:21:55 -0400	[thread overview]
Message-ID: <db9a7e24-1d99-4ff5-8827-396263cbcec5@app.fastmail.com> (raw)
In-Reply-To: <20231002121149.2325402-3-adhemerval.zanella@linaro.org>

On Mon, Oct 2, 2023, at 8:11 AM, Adhemerval Zanella wrote:
> All the crypt related functions, cryptographic algorithms, and
> make requirements are removed,  with only the exception of md5
> implementation which is moved to locale folder since it is
> required by localedef for integrity protection (libc's
> locale-reading code does not check these, but localedef does
> generate them).

LGTM, albeit I did not check for any surviving references to libcrypt
or the crypt subdirectory.

zw

  reply	other threads:[~2023-10-02 14:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 12:11 [PATCH v2 0/2] " Adhemerval Zanella
2023-10-02 12:11 ` [PATCH v2 1/2] sparc: Remove optimize md5, sha256, and sha512 Adhemerval Zanella
2023-10-30 12:52   ` Carlos O'Donell
2023-10-30 13:04     ` Carlos O'Donell
2023-10-02 12:11 ` [PATCH v2 2/2] crypt: Remove libcrypt support Adhemerval Zanella
2023-10-02 14:21   ` Zack Weinberg [this message]
2023-10-30 12:52   ` Carlos O'Donell
2023-10-31 13:43     ` Joseph Myers
2023-10-31 14:00       ` Adhemerval Zanella Netto
2024-01-16 12:00   ` Szabolcs Nagy
2024-01-16 12:21     ` Andreas Schwab
2023-10-30 12:52 ` [PATCH v2 0/2] " Carlos O'Donell

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=db9a7e24-1d99-4ff5-8827-396263cbcec5@app.fastmail.com \
    --to=zack@owlfolio.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).