From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: libc-alpha@sourceware.org,
Stephen Roettger <sroettger@google.com>,
jeffxu@chromium.org, Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [RFC 3/5] elf: Add support to memory sealing
Date: Tue, 11 Jun 2024 18:03:11 -0300 [thread overview]
Message-ID: <378E1893-4F36-438F-93D2-EBA3B44D38DA@linaro.org> (raw)
In-Reply-To: <87jzivryte.fsf@trenco.lwn.net>
> On 11 Jun 2024, at 17:47, Jonathan Corbet <corbet@lwn.net> wrote:
> Adhemerval Zanella <adhemerval.zanella@linaro.org> writes:
>
>> The sealing is controlled by a new tunable, glibc.rtld.seal, with
>> three different states:
>>
>> 0. Disabled where no sealing is done. This is the default.
>>
>> 1. Enabled, where the loader will issue the mseal syscall on the
>> memory mappings but any failure will be ignored. This is
>> the default.
>>
>> 2. Enforce, similar to Enabled but any failure from the mseal
>> will terminate the process.
>
> Cool - two defaults! :)
>
> It *looks* like the actual default is 0?
>
> Thanks,
>
> jon
Oops, the actual default is 1 (apply, not enforce). I will fix the commit message.
next prev parent reply other threads:[~2024-06-11 21:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 15:27 [RFC 0/5] Add support for " Adhemerval Zanella
2024-06-11 15:27 ` [RFC 1/5] linux: Remove __stack_prot Adhemerval Zanella
2024-06-11 19:15 ` Florian Weimer
2024-06-11 15:27 ` [RFC 2/5] linux: Add mseal syscall support Adhemerval Zanella
2024-06-11 15:27 ` [RFC 3/5] elf: Add support to memory sealing Adhemerval Zanella
2024-06-11 20:47 ` Jonathan Corbet
2024-06-11 21:03 ` Adhemerval Zanella [this message]
2024-06-21 5:09 ` Mike Hommey
2024-06-25 21:07 ` Adhemerval Zanella Netto
2024-06-25 23:18 ` Mike Hommey
2024-06-26 11:58 ` Adhemerval Zanella Netto
2024-06-26 19:58 ` Mike Hommey
2024-06-26 21:20 ` Adhemerval Zanella Netto
2024-06-26 21:39 ` Mike Hommey
2024-06-26 21:56 ` Adhemerval Zanella Netto
2024-06-27 23:00 ` Mike Hommey
2024-06-28 5:51 ` Florian Weimer
2024-06-28 5:58 ` Mike Hommey
2024-06-28 6:06 ` Florian Weimer
2024-06-28 7:39 ` Mike Hommey
2024-07-01 21:08 ` Adhemerval Zanella Netto
2024-06-11 15:27 ` [RFC 4/5] elf: Enable RTLD_NODELETE on __libc_unwind_link_get Adhemerval Zanella
2024-06-12 9:54 ` Florian Weimer
2024-06-12 17:16 ` Adhemerval Zanella Netto
2024-06-12 17:50 ` Florian Weimer
2024-06-12 17:55 ` Adhemerval Zanella Netto
2024-06-11 15:27 ` [RFC 5/5] elf: Add support to memory sealing for audit modules 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=378E1893-4F36-438F-93D2-EBA3B44D38DA@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=corbet@lwn.net \
--cc=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).