From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] New configure option --disable-crypt.
Date: Mon, 25 Jun 2018 16:28:12 +0200 [thread overview]
Message-ID: <2fca972e-cf3d-a560-6475-a1a71c660bd9@redhat.com> (raw)
In-Reply-To: <20180625142050.GA26140@altlinux.org>
On 06/25/2018 04:20 PM, Dmitry V. Levin wrote:
> On Mon, Jun 25, 2018 at 03:44:03PM +0200, Florian Weimer wrote:
> [...]
>> diff --git a/NEWS b/NEWS
>> index d43d11dce1..556db82643 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -127,6 +127,18 @@ Deprecated and removed features, and other changes affecting compatibility:
>> binaries. It was just another name for the standard function crypt,
>> and it has not appeared in any header file in many years.
>>
>> +* We have tentative plans to hand off maintenance of the passphrase-hashing
>> + library, libcrypt, to a separate development project that will, we hope,
>> + keep up better with new passphrase-hashing algorithms. We will continue
>> + to declare 'crypt' in <unistd.h>, and programs that use 'crypt' or
>> + 'crypt_r' should not need to change at all; however, distributions will
>> + need to install <crypt.h> and libcrypt from the separate project.
>
> from a separate project.
Thanks, fixed locally.
Florian
next prev parent reply other threads:[~2018-06-25 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 13:44 [PATCH] New configure option --disable-crypt Florian Weimer
2018-06-25 13:47 ` Florian Weimer
2018-06-25 14:20 ` Dmitry V. Levin
2018-06-25 14:28 ` Florian Weimer [this message]
2018-06-28 17:33 ` Dmitry V. Levin
2018-06-28 18:23 ` Florian Weimer
2018-06-28 21:20 ` Dmitry V. Levin
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2fca972e-cf3d-a560-6475-a1a71c660bd9@redhat.com \
--to=fweimer@redhat.com \
--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).