linux-kernel - Fwd: CET shadow stack app compatibility

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAOGzEzfvPHTuuCAEx1n4zVxHF6JT63oHu1nfRfaxuJBKGZxtCw@mail.gmail.com>
Date:   Tue, 15 Nov 2022 16:08:41 +0100
From:   lkml gm4 <lkml4gm@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Fwd: CET shadow stack app compatibility

* Linus Torvalds:

> I'm disgusted by glibc being willing to just upgrade and break
> existing binaries and take the "you shouldn't upgrade glibc if you
> have old binaries" approach.

But glibc also claims this policy:

https://www.gnu.org/software/libc/
says:
The GNU C Library is designed to be a backwards compatible,

And
https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html
Thus, program binaries linked with the initial release of a library
binary will still run correctly if the library binary is replaced by
carefully-managed subsequent library binaries.

And glibc even has it easier then the kernel: implement incompatible
changes by applying
symbol versioning.

-
lkml4gm