From: Farid Zakaria <fmzakari@ucsc.edu>
To: libc-help@sourceware.org
Subject: Re: How can I wrap ld-linux or execve into it?
Date: Mon, 31 Jan 2022 12:29:21 -0800 [thread overview]
Message-ID: <CAH4OOv4MU36mCrsu9FtP2Fz1iD5xfDpBuQ91jrKVRc0WRYMsYQ@mail.gmail.com> (raw)
In-Reply-To: <CAH4OOv4bJA8xpPfEyBs3bOG4ijzz=fh4pwRgVTtHk3bcvroNpA@mail.gmail.com>
Adding some more context based on some private responses:
My goal is to explore some potential changes as part of a PhD thesis
to control dynamic linking.
I have explored modifying glibc/musl but I was exploring an execve approach to:
1. make the change libc agnostic
2. restrict my changes to a smaller codebase for the purpose of the exploration
On Mon, Jan 31, 2022 at 12:10 PM Farid Zakaria <fmzakari@ucsc.edu> wrote:
>
> Hi,
>
> I am looking to perform some functionality before the dynamic linker
> (linux-ld/ld.so) is invoked.
>
> My naive assessment was that I would be able to set in the PT_INTERP
> section of a binary, my *static binary*, which will then execve into
> the dynamic linker after doing some precanned actions.
>
> Unfortunately, trying this has resulted in some SIGSEGV...
>
> I came across https://github.com/Mic92/nix-ld which seems to do
> something similar, but I was curious why it has to do a lot more to
> achieve the same effect with a jump.
>
> I have also been pointed to LD_AUDIT however I am also interested in
> having it agnostic to libc (glibc vs. musl)
>
> Thank you for any tips, guidance or links you can provide.
> FZ
next prev parent reply other threads:[~2022-01-31 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:10 Farid Zakaria
2022-01-31 20:29 ` Farid Zakaria [this message]
2022-02-01 12:43 ` Adhemerval Zanella
2022-02-01 17:14 ` Farid Zakaria
2022-02-01 17:49 ` Adhemerval Zanella
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=CAH4OOv4MU36mCrsu9FtP2Fz1iD5xfDpBuQ91jrKVRc0WRYMsYQ@mail.gmail.com \
--to=fmzakari@ucsc.edu \
--cc=libc-help@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).