[Security-sig] Does the buildtime HAVE_GETRANDOM_SYSCALL check actually make sense?

Nick Coghlan ncoghlan at gmail.com
Sun Jul 3 02:30:27 EDT 2016


On 26 June 2016 at 02:30, Victor Stinner <victor.stinner at gmail.com> wrote:
> The configure check ensures that constants required to build random.c are
> available. We can only run this check at the compilation. I don't want to
> maintain hardcoded constants.
>
> The proper fix is to add getrandom() to the libc:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17252
>
> But you may have the same issue if you build the lib with "old" header
> files.

mock (the Fedora build utility, not the Python testing utility) will
use the updated header files when building against the newer glibc, so
not worrying about this until it's resolved there sounds fine to me.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia


More information about the Security-SIG mailing list