This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v2] libio: use PTR_MANGLE/PTR_DEMANGLE for FILE vtables
- From: Kees Cook <keescook at chromium dot org>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Florian Weimer <fweimer at redhat dot com>, libc-alpha <libc-alpha at sourceware dot org>, Mike Frysinger <vapier at gentoo dot org>, Adam Conrad <adconrad at 0c3 dot net>
- Date: Thu, 1 Oct 2015 15:27:08 -0700
- Subject: Re: [PATCH v2] libio: use PTR_MANGLE/PTR_DEMANGLE for FILE vtables
- Authentication-results: sourceware.org; auth=none
- References: <20151001184048 dot GA31563 at www dot outflux dot net> <560D8108 dot 6060802 at redhat dot com> <alpine dot DEB dot 2 dot 10 dot 1510012059180 dot 9824 at digraph dot polyomino dot org dot uk> <CAGXu5jLbUeqy9+Q9KOVGaD=s_HQtz2bbyaFmNfcUf2n+9yqesQ at mail dot gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1510012140380 dot 9824 at digraph dot polyomino dot org dot uk>
On Thu, Oct 1, 2015 at 2:41 PM, Joseph Myers <joseph@codesourcery.com> wrote:
> On Thu, 1 Oct 2015, Kees Cook wrote:
>
>> On Thu, Oct 1, 2015 at 2:00 PM, Joseph Myers <joseph@codesourcery.com> wrote:
>> > On Thu, 1 Oct 2015, Florian Weimer wrote:
>> >
>> >> Even better, if we can grab a few old binaries and they do not run on
>> >> current systems for other libstdc++-related reasons (or perhaps we
>> >
>> > The libstdc++ SONAME changed in GCC 3.4, so any relevant binaries will be
>> > using an old libstdc++ shared library (or possibly statically linked with
>> > libstdc++ but dynamically linked with libc).
>>
>> So system without ancient static binaries and no libstdc++-v3 or
>> earlier should be safe for this change? When did v4 happen? Seems like
>> a long time ago?
>
> It's still libstdc++-v3 even though it's gone through multiple SONAMEs
> (it's been v3 since GCC 3.0). The question is libstdc++.so.5 or older -
> or dynamically linked binaries from compilers of that vintage with
> libstdc++.a linked in.
Okay, so, since roughly 2007? Should I name the config "--only-v6+" or
something?
-Kees
--
Kees Cook
Chrome OS Security