From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, Philipp Stephani <phst@google.com>,
Robert Pluim <rpluim@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
emacs-devel@gnu.org
Subject: Re: emacs-28 6d3608be88: Seccomp: improve support for newer versions of glibc (Bug#51073)
Date: Tue, 25 Jan 2022 21:12:17 +0100 [thread overview]
Message-ID: <E6C12F65-A269-4A4C-AE1A-B972B9DBC199@gmail.com> (raw)
In-Reply-To: <83bl01jbks.fsf@gnu.org>
> Am 24.01.2022 um 18:19 schrieb Eli Zaretskii <eliz@gnu.org>:
>
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Lars Ingebrigtsen <larsi@gnus.org>, luangruo@yahoo.com,
>> phst@google.com, p.stephani2@gmail.com, emacs-devel@gnu.org
>> Date: Mon, 24 Jan 2022 17:47:19 +0100
>>
>> Eli> It is very worrisome that a change in glibc can break Emacs like that.
>> Eli> I wonder what it means for the maintainability of Emacs in the long
>> Eli> run. I have a bad feeling about this.
>>
>> We can always default the seccomp support to off.
>
> If it's so fragile, perhaps we should.
The seccomp support isn't fragile at all. It only relies on the Linux kernel and a small number of syscalls that haven't changed for a long time.
What is "fragile" here (though I think this wording is incorrect) is the generation of the default filter that we ship for convenience reasons. That one should be adapted (maybe a few times per year, so not very frequently) to newer libc versions. There's no other way since unknown syscalls in the filter can't be allowed for security reasons.
next prev parent reply other threads:[~2022-01-25 20:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164286838577.8429.4021499312049157333@vcs2.savannah.gnu.org>
[not found] ` <20220122161946.44098C0DA30@vcs2.savannah.gnu.org>
2022-01-24 0:08 ` emacs-28 6d3608be88: Seccomp: improve support for newer versions of glibc (Bug#51073) Po Lu
2022-01-24 10:44 ` Philipp Stephani
2022-01-24 12:53 ` Eli Zaretskii
2022-01-24 13:33 ` Po Lu
2022-01-24 13:41 ` Eli Zaretskii
2022-01-24 14:38 ` Lars Ingebrigtsen
2022-01-24 15:00 ` Eli Zaretskii
2022-01-24 16:47 ` Robert Pluim
2022-01-24 17:19 ` Eli Zaretskii
2022-01-25 20:12 ` Philipp Stephani [this message]
2022-01-26 3:23 ` Eli Zaretskii
2022-01-25 20:09 ` Philipp Stephani
2022-01-25 21:40 ` Stefan Monnier
2022-01-26 3:22 ` Eli Zaretskii
2022-01-25 4:16 ` Richard Stallman
2022-01-25 12:08 ` Eli Zaretskii
2022-01-25 20:13 ` Philipp Stephani
2022-01-26 3:24 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E6C12F65-A269-4A4C-AE1A-B972B9DBC199@gmail.com \
--to=p.stephani2@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=phst@google.com \
--cc=rpluim@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).