linux-hardening - Re: mips gcc plugin issues

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] [day] [month] [year] [list]

Message-Id: <345dff33-86f0-4de3-90e3-9e3a13f20875@app.fastmail.com>
Date: Thu, 20 Jun 2024 07:10:13 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Kees Cook" <kees@...nel.org>
Cc: "Jeff Johnson" <quic_jjohnson@...cinc.com>,
 linux-hardening@...r.kernel.org, "open list" <linux-kernel@...r.kernel.org>
Subject: Re: mips gcc plugin issues

On Wed, Jun 19, 2024, at 23:17, Kees Cook wrote:
> On Wed, Jun 19, 2024 at 11:12:25PM +0200, Arnd Bergmann wrote:
>> On Wed, Jun 19, 2024, at 22:50, Kees Cook wrote:

>> The problem here is that a gcc plugin links against the
>> compiler, not against code produced by it. I'm linking the
>> crosstool compilers statically against libraries as much as
>> possible in order to make them more portable between distros,
>> but the downside of that is that plugins will only work in
>> the environment that I was using to build these toolchains.
>> 
>> My build environment is an older Debian (in order to be
>> portable to old glibc versions), but with the system compiler
>> updated to gcc-13 (since x86 libgcc cannot be cross-compiled
>> with an older compiler).
>
> Can the crosstools remove the plugin support? That seems like the best
> solution. Kconfig test for plugin availability with:
>
> 	depends on $(success,test -e $(shell,$(CC) 
> -print-file-name=plugin)/include/plugin-version.h)

Good idea, yes. I still have to upload gcc-14.1 and gcc-13.3 binaries
anyway, so I'll try turning off plugin support when I build it.

      Arnd