From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: luangruo@yahoo.com, phst@google.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs-28 6d3608be88: Seccomp: improve support for newer versions of glibc (Bug#51073)
Date: Wed, 26 Jan 2022 05:24:41 +0200 [thread overview]
Message-ID: <831r0vi3gm.fsf@gnu.org> (raw)
In-Reply-To: <3915003C-0382-4F0A-9789-7072660BE158@gmail.com> (message from Philipp Stephani on Tue, 25 Jan 2022 21:13:38 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Tue, 25 Jan 2022 21:13:38 +0100
> Cc: rms@gnu.org,
> Po Lu <luangruo@yahoo.com>,
> Philipp Stephani <phst@google.com>,
> emacs-devel@gnu.org
>
>
>
> > Am 25.01.2022 um 13:08 schrieb Eli Zaretskii <eliz@gnu.org>:
> >
> >> From: Richard Stallman <rms@gnu.org>
> >> Date: Mon, 24 Jan 2022 23:16:03 -0500
> >> Cc: luangruo@yahoo.com, phst@google.com, emacs-devel@gnu.org
> >>
> >>> That can happen any day, if glibc folks make some change we didn't
> >>> know about. We cannot chase glibc development forever, we will never
> >>> succeed catching up with them, certainly not in the long run.
> >>
> >> It's true that problems like this can happen any day. Not just with
> >> Glibc but with lots of libraries that Emacs uses. But that has been
> >> the case for many years. Are things getting worse in some way?
> >
> > If frequent changes to glibc cause Emacs to crash, that is bad.
>
> These "crashes" are the whole point and purpose of seccomp filters. If an Emacs process is sandboxed using a syscall filter, any unknown syscall has to exit the process ("crash"), otherwise the sandbox would be insecure.
The important point is that it makes Emacs unusable in this mode.
Perhaps security-wise this is what you want, but I very much doubt
that users will be pleased.
prev parent reply other threads:[~2022-01-26 3:24 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
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 [this message]
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=831r0vi3gm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=p.stephani2@gmail.com \
--cc=phst@google.com \
--cc=rms@gnu.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.
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).