From: Florian Weimer <fweimer@redhat.com>
To: Stephen Roettger <sroettger@google.com>
Cc: libc-alpha@sourceware.org, jeffxu@chromium.org
Subject: Re: [RFC 0/1] elf: mseal non-writable segments
Date: Wed, 22 May 2024 21:42:01 +0200 [thread overview]
Message-ID: <87sey9eira.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20240522112933.2005066-1-sroettger@google.com> (Stephen Roettger's message of "Wed, 22 May 2024 13:29:30 +0200")
* Stephen Roettger:
> In my basic testing, this seems to work fine. But a few questions that
> I'd like some feedback on:
> * Does it sound ok to apply sealing by default? Should this be a flag in
> the ELF, e.g. maybe the p_flags could have a sealable bit?
It depends on how the integration with RELRO should look like.
> * Does it make sense to piggyback on the RTLD_NODELETE bit and apply it
> to more objects? It seems to have the right semantics: the object
> should never get deleted => it's ok to seal the mappings.
Doesn't this inhibit many forms of debugging? We wouldn't want to do
that by default, I think.
Thanks,
Florian
next prev parent reply other threads:[~2024-05-22 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 11:29 Stephen Roettger
2024-05-22 11:29 ` [RFC 1/1] " Stephen Roettger
2024-05-22 16:24 ` Cristian Rodríguez
[not found] ` <CAEAAPHaEssoE79B0vWk1S42QaUk+WVwJ0sNxnUzF3hkXNG+b9w@mail.gmail.com>
2024-05-22 18:39 ` Carlos O'Donell
2024-05-22 18:57 ` [RFC 0/1] " Carlos O'Donell
2024-05-23 9:31 ` Stephen Röttger
2024-05-23 10:38 ` Florian Weimer
2024-05-22 19:42 ` Florian Weimer [this message]
2024-05-23 9:36 ` Stephen Röttger
2024-06-04 14:19 ` Adhemerval Zanella Netto
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=87sey9eira.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=jeffxu@chromium.org \
--cc=libc-alpha@sourceware.org \
--cc=sroettger@google.com \
/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).