linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Parschauer <s.parschauer@gmx.de>
To: Michael Davidson <md@google.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Jiri Kosina <jkosina@suse.cz>, Kees Cook <keescook@chromium.org>,
	linux-fsdevel@vger.kernel.org,
	Sebastian Parschauer <S.Parschauer@gmx.de>
Subject: Re: [PATCH] binfmt_elf: Fix bug in loading of PIE binaries
Date: Thu, 16 Jul 2015 21:57:25 +0200	[thread overview]
Message-ID: <55A80CA5.2000104@gmx.de> (raw)
In-Reply-To: 1428965343-17762-1-git-send-email-md@google.com

Hi,

I'm a professional Linux game cheater and the co-maintainer of scanmem.
With scanmem we determine the load addresses for PIC and PIE binaries to
be able to support static memory cheating with ASLR. At the moment
ugtrain is the only universal game trainer able to determine the PIE
load address as well and to re-add it to the found match offset from
scanmem.

I'd like to complain a bit about this patch as it makes the address
space layout for the executable really ugly by loading unrelated stuff
between .text and .rodata.

Is it really required on top of 3.13 or 3.16 where Ubuntu has put it?

I've also checked v4.2-rc1. There everything is beautiful again.
Thank you very much for that!

References:
https://github.com/scanmem/scanmem/issues/122
https://github.com/ugtrain/ugtrain

Thanks,
Sebastian

             reply	other threads:[~2015-07-16 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 19:57 Sebastian Parschauer [this message]
2015-07-16 20:34 ` [PATCH] binfmt_elf: Fix bug in loading of PIE binaries Kees Cook
2015-07-19 20:28   ` Sebastian Parschauer
2015-08-08 21:36   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2015-04-13 22:49 Michael Davidson
2015-05-19 15:01 ` James Hogan

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=55A80CA5.2000104@gmx.de \
    --to=s.parschauer@gmx.de \
    --cc=jkosina@suse.cz \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=md@google.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 NNTP newsgroup(s).