From: Joseph Myers <joseph@codesourcery.com>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>, Rical Jasan <rj@2c3t.io>,
Thorsten Kukuk <kukuk@suse.de>
Subject: Re: [PATCH 4/4] New configure option --disable-crypt.
Date: Mon, 21 May 2018 22:34:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1805212226550.30181@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAKCAbMi5-c+nrt3apH-rnvi1jX+4ShLJ140ZvzjqEGrcoETs9w@mail.gmail.com>
On Mon, 21 May 2018, Zack Weinberg wrote:
> On Mon, May 21, 2018 at 3:51 PM, Joseph Myers <joseph@codesourcery.com> wrote:
> > On Mon, 21 May 2018, Zack Weinberg wrote:
> >
> >> unistd.h continues to define _XOPEN_CRYPT to 1 and to declare crypt.
> >
> > I'd expect _XOPEN_CRYPT to change in patch 1, since it includes encrypt
> > and setkey.
>
> No, this is an intentional deviation from the present state of POSIX,
> anticipating the removal of those functions from the standard.
That would only seem relevant to the _XOPEN_CRYPT value in future POSIX
modes, not current ones.
The conform/ data is in any case meant to correspond to the standard
versions in question (plus defect corrections from TCs etc., not plus
feature changes from other revisions to the standard). Intentionally
unsupported features are listed in that data with appropriate XFAILs (see
e.g. those for varargs.h in conform/Makefile).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-05-21 22:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 17:39 [PATCH 0/4 v3] libcrypt phaseout Zack Weinberg
2018-05-21 17:39 ` [PATCH 4/4] New configure option --disable-crypt Zack Weinberg
2018-05-21 19:52 ` Joseph Myers
2018-05-21 22:07 ` Zack Weinberg
2018-05-21 22:34 ` Joseph Myers [this message]
2018-05-22 1:08 ` Zack Weinberg
2018-06-20 20:40 ` Florian Weimer
2018-06-20 22:48 ` Zack Weinberg
2018-06-21 9:31 ` Florian Weimer
2018-06-21 9:32 ` Florian Weimer
2018-06-28 18:52 ` Zack Weinberg
2018-05-21 17:39 ` [PATCH 3/4] Revise crypt.texi Zack Weinberg
2018-05-25 2:52 ` Rical Jasan
2018-06-25 12:21 ` Florian Weimer
2018-06-25 12:26 ` Florian Weimer
2018-05-21 17:39 ` [PATCH 1/4] Disallow use of DES encryption functions in new programs Zack Weinberg
2018-05-22 6:58 ` Florian Weimer
2018-05-23 3:37 ` Rical Jasan
2018-05-23 16:50 ` Joseph Myers
2018-05-21 17:39 ` [PATCH 2/4] Reorganize crypt.texi Zack Weinberg
2018-05-23 5:23 ` Rical Jasan
-- strict thread matches above, loose matches on Subject: below --
2018-05-06 17:52 [PATCH 0/4 v3] Revise crypto documentation, deprecate DES, add --disable-crypt Zack Weinberg
2018-05-06 17:52 ` [PATCH 4/4] New configure option --disable-crypt Zack Weinberg
2018-05-08 15:00 ` Florian Weimer
2018-05-08 15:22 ` Zack Weinberg
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=alpine.DEB.2.20.1805212226550.30181@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=kukuk@suse.de \
--cc=libc-alpha@sourceware.org \
--cc=rj@2c3t.io \
--cc=zackw@panix.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).