From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Should we make DT_HASH dynamic section for glibc?
Date: Tue, 09 Aug 2022 11:21:21 +0200 [thread overview]
Message-ID: <87bkstn566.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <e2918326-9329-4195-6e9a-747829f3126e@redhat.com> (Carlos O'Donell via Libc-alpha's message of "Mon, 8 Aug 2022 16:40:49 -0400")
* Carlos O'Donell via Libc-alpha:
>> So the question is whether we should enforce at least on glibc by reverting
>> e47de5cb2d4dbec. It does sounds muddle to keep this solely on glibc, where
>> rest of the system is not enforcing it, and only for compatibility with an
>> obscure tools where there is no much information on why it requires it.
>
> The tool is EAC.
>
> It is EPICs "Easy Anti-Cheat" (https://www.easy.ac/en-us/) and like
> other non-standard consumers it has to know some specific ELF details.
>
> The game "Rogue Company" is known to use EAC and is likely broken by
> this change.
I think there are several other glibc patches required to fix Rogue
Company?
<https://github.com/GloriousEggroll/glibc-eac-rc> (“glibc with reverts
applied to allow Rogue Company to work with EasyAntiCheat”) makes the
following changes:
· Install shared objects under traditional versioned nmaes.
· Bring back various GLIBC_PRIVATE symbols.
· Disable clone3.
If EasyAntiCheat has been fixed for those, surely it can be fixed to use
DT_GNU_HASH as well.
THanks,
Florian
next prev parent reply other threads:[~2022-08-09 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:31 Adhemerval Zanella Netto
2022-08-08 20:40 ` Carlos O'Donell
2022-08-08 20:56 ` Carlos O'Donell
2022-08-08 22:59 ` Fangrui Song
2022-08-08 23:36 ` Sam James
2022-08-09 9:21 ` Florian Weimer [this message]
2022-09-30 12:56 ` Carlos O'Donell
2022-10-01 7:40 ` Fangrui Song
2022-10-01 8:31 ` Sam James
2022-10-01 8:41 ` Andreas Schwab
2022-10-01 13:49 ` Florian Weimer
2022-10-03 20:57 ` Michael Hudson-Doyle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkstn566.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).