public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	"Carlos O'Donell" <carlos@redhat.com>,
	 Nikos Mavrogiannopoulos <nmav@redhat.com>
Subject: Re: [PATCH] New configure option --disable-libcrypt.
Date: Wed, 18 Apr 2018 13:43:00 -0000	[thread overview]
Message-ID: <CAKCAbMizfEOjvQZRXqCrf=dDUEdkdZHs0RYS4d5az1enR3NVog@mail.gmail.com> (raw)
In-Reply-To: <ac70eb58-98fb-07b3-bf78-0e54ebcf382b@redhat.com>

On Tue, Apr 17, 2018 at 6:21 AM, Florian Weimer <fweimer@redhat.com> wrote:
> On 04/16/2018 05:56 PM, Zack Weinberg wrote:
>
>> Let me see if I understand what you have in mind:  In
>> --disable-libcrypt mode, we would preserve _XOPEN_CRYPT, with value 1,
>> and the prototype for crypt in unistd.h.
>
> My main proposal is preserving the prototype for crypt, under _GNU_SOURCE if
> necessary (without defining _XOPEN_CRYPT).
>
> I just don't see value in the friction caused by dropping the definition.

Makes sense.

> It could still be a conformance violation for setkey/encrypt because current
> libxcrypt (at least the version in Fedora) does not provide the functions
> anymore for linking:
>
> $ eu-readelf --symbols=.dynsym /lib64/libcrypt.so.1 | grep encrypt
>    38: 000000000000b330     20 FUNC    GLOBAL DEFAULT       12
> encrypt_r@GLIBC_2.2.5
>    52: 000000000000b360     16 FUNC    GLOBAL DEFAULT       12
> encrypt@GLIBC_2.2.5

Yeah, I did that on purpose; the total insecurity of single DES
outweighs standard compliance in this case, I think.  And, as you say,
there probably aren't very many users.

I'll send a revised patch shortly.

zw

      reply	other threads:[~2018-04-18 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16  1:36 Zack Weinberg
2018-04-16 15:11 ` Florian Weimer
2018-04-16 15:56   ` Zack Weinberg
2018-04-16 18:41     ` Zack Weinberg
2018-04-17 10:21     ` Florian Weimer
2018-04-18 13:43       ` Zack Weinberg [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='CAKCAbMizfEOjvQZRXqCrf=dDUEdkdZHs0RYS4d5az1enR3NVog@mail.gmail.com' \
    --to=zackw@panix.com \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nmav@redhat.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).