linux-kernel - Re: Static call dependency on libelf version?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <38388294c6ad7bf4abdb1b9a0bac9af5224c8fa6.camel@klomp.org>
Date:   Tue, 15 Sep 2020 16:38:02 +0200
From:   Mark Wielaard <mark@...mp.org>
To:     Josh Poimboeuf <jpoimboe@...hat.com>
Cc:     peterz@...radead.org, Hugh Dickins <hughd@...gle.com>,
        linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: Static call dependency on libelf version?

Hi Josh,

On Tue, 2020-09-15 at 09:17 -0500, Josh Poimboeuf wrote:
> On Tue, Sep 15, 2020 at 01:24:17PM +0200, Mark Wielaard wrote:
> > But all this is for ancient versions of elfutils libelf. So it is hard
> > to say and my memory might be failing. If someone can confirm 0.158
> > (which is 6 years old) works fine I would pick that as minimum version,
> > otherwise simply go with 0.168 which is 4 years old and should be on
> > most systems by now.
> 
> I just discovered elf_version(), I assume that would allow us to check
> and enforce the libelf version?

No, sorry. That is for the ELF file format version, which is and has
always been  version 1 (and I suspect it will be for the next 20
years).

There is /usr/include/elfutils/version.h which provides a
_ELFUTILS_PREREQ(major, minor) macro if you need something during
compile time.

Note that in theory libelf is a generic library (there are variants for
Solaris and BSD with which we try to be [source] compatible), but the
only actively maintained version is the elfutils one.

Cheers,

Mark