From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-75571-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 107290 invoked by alias); 6 Dec 2016 17:14:55 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 107269 invoked by uid 89); 6 Dec 2016 17:14:54 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=
X-HELO: mail-qk0-f193.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:subject:to:references:cc:from:message-id:date
         :user-agent:mime-version:in-reply-to:content-transfer-encoding;
        bh=B+mQKUV23DGqGCV0gs0GIgv4f71I8xAMJR230DAk9Gs=;
        b=dJvafNH7teo1Xk7u/WKZXHiIqHuFXkvpn4+i7fCQFu9bmQI1HxUVBEJV3jIaXGyPEi
         hOq4bQxmLiQuptwoOXo3dfffS48itW2bc7hQfasnWkSHseaS9QJa26Ebzi7FWzjm7GIQ
         aD1pgMViKZTWVWHt64AD2g5I30/TtLJMfKe5o/ssiZjJn01o0xRHIy/KDo5zYwQQkoct
         +T6OybjC0xcgrXM1vDqDw0ggnO44eGzgVgfA6RQSnuWK7lWLt/kftGVqmjMAKf+/xZge
         /VPCM4s45GAUR5mn8jWPdwSAd5vpn2aaQhHJFFo9WZkmIQwA/GSMRlvM4kh61IspLFb/
         zSsg==
X-Gm-Message-State: AKaTC00xgISKBzaMTKkhJ3Rdgh46H4I7uihiogzO7oep1wmZEjNWfC2K5z8pQyCQqbOY4A==
X-Received: by 10.55.131.71 with SMTP id f68mr3125583qkd.207.1481044487610;
        Tue, 06 Dec 2016 09:14:47 -0800 (PST)
Subject: Re: [PATCH v9] Add getentropy, getrandom, <sys/random.h> [BZ #17252]
To: Joseph Myers <joseph@codesourcery.com>
References: <5b8e5866-d071-9e2c-54e7-2ccf857a2fd8@redhat.com>
 <97f4db91-49d9-83fa-9f67-6cc718629160@redhat.com>
 <1480697250.14990.52.camel@redhat.com>
 <680d0bed-b164-b809-d672-e0278fe08d7e@redhat.com>
 <90908be7-c7db-46f2-a635-27dc5604e47f@panix.com>
 <alpine.DEB.2.20.1612061636050.16077@digraph.polyomino.org.uk>
 <9b5ff44f-deaf-4126-9d49-dbe30f14ef82@panix.com>
 <alpine.DEB.2.20.1612061652240.16077@digraph.polyomino.org.uk>
Cc: Florian Weimer <fweimer@redhat.com>, Torvald Riegel <triegel@redhat.com>,
 GNU C Library <libc-alpha@sourceware.org>
From: Zack Weinberg <zackw@panix.com>
Message-ID: <ccf15c57-fca8-8e42-2e06-dc853c4993bd@panix.com>
Date: Tue, 06 Dec 2016 17:14:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Icedove/45.5.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1612061652240.16077@digraph.polyomino.org.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-SW-Source: 2016-12/txt/msg00199.txt.bz2

On 12/06/2016 11:55 AM, Joseph Myers wrote:
> On Tue, 6 Dec 2016, Zack Weinberg wrote:
> 
>> On the assumption that this _is_ the issue, I am going to write a script
>> that scans the Debian archive for existing binaries containing
>> definitions (exported or not) of getentropy and/or getrandom, and will
>> report what it tells me -- this will probably take a couple days to
>> cycle all the way through.
> 
> You can't generally tell for a stripped executable whether there's a 
> getentropy function in there - only if it's unstripped, or linked with 
> -rdynamic, or linked with glibc that defines getentropy and so exports it 
> in the dynamic symbol table for that reason.  You could scan shared 
> libraries for bogus exports, but I don't see how you could test for 
> executables that would cause a problem when linked with new glibc without 
> doing a full archive rebuild with patched glibc.

Oh bother.  Well, forget that idea - I don't have access to sufficient
CPU grunt to do an archive rebuild.

zw