This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Running old binaries that abuses setjmp/longjmp with recent glibc
- From: Viktor Ostashevskyi <ostash at ostash dot kiev dot ua>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: libc-help at sourceware dot org
- Date: Fri, 17 Jan 2020 23:05:19 +0100
- Subject: Re: Running old binaries that abuses setjmp/longjmp with recent glibc
- References: <CAJ4BaJGf4=1+LXFNn9Cuv_H6dY6xeMwaXcOp-Pynrd9Pkr23_w@mail.gmail.com> <87y2u521km.fsf@oldenburg2.str.redhat.com>
Hello,
пт, 17 січ. 2020 о 22:52 Florian Weimer <fweimer@redhat.com> пише:
> We could perhaps add a tunable that allows the user to disable the
> hardening at process startup, e.g., instead of XORing with a random
> value, always XOR with zero. The cost for that would be quite small.
Wasn't it you who removed such tunable in
https://sourceware.org/git/?p=glibc.git;a=commit;h=a014cecd82b71b70a6a843e250e06b541ad524f7
? :)
And XOR'ing with 0 won't help, I've tried by reverting your commit
setting LD_POINTER_GUARD=1.
Current mangling on i386 applies shift with rotation after XORing. So
at least on i386 pointers were still mangled even with
LD_POINTER_GUARD=1.
--
З повагою, Осташевський Віктор