From: Joseph Myers <joseph@codesourcery.com>
To: Zack Weinberg <zackw@panix.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Torvald Riegel <triegel@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v9] Add getentropy, getrandom, <sys/random.h> [BZ #17252]
Date: Tue, 06 Dec 2016 16:55:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1612061652240.16077@digraph.polyomino.org.uk> (raw)
In-Reply-To: <9b5ff44f-deaf-4126-9d49-dbe30f14ef82@panix.com>
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.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-12-06 16:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 13:33 [PATCH v8] " Florian Weimer
2016-11-30 16:15 ` [PATCH v9] " Florian Weimer
2016-12-02 16:47 ` Torvald Riegel
2016-12-06 12:55 ` Florian Weimer
2016-12-06 13:41 ` Zack Weinberg
2016-12-06 14:03 ` Florian Weimer
2016-12-06 17:11 ` Zack Weinberg
2016-12-06 18:42 ` Zack Weinberg
2016-12-07 11:18 ` Florian Weimer
2016-12-07 14:47 ` Zack Weinberg
2016-12-06 16:42 ` Joseph Myers
2016-12-06 16:51 ` Zack Weinberg
2016-12-06 16:55 ` Joseph Myers [this message]
2016-12-06 16:59 ` Florian Weimer
2016-12-06 17:02 ` Joseph Myers
2016-12-07 10:52 ` Florian Weimer
2016-12-06 17:14 ` 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.1612061652240.16077@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=triegel@redhat.com \
--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).