From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: luangruo@yahoo.com, phst@google.com, larsi@gnus.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:22:51 +0200 [thread overview]
Message-ID: <834k5ri3jo.fsf@gnu.org> (raw)
In-Reply-To: <17E6AEF0-D704-44FB-8B2F-6DCDE67EE22F@gmail.com> (message from Philipp Stephani on Tue, 25 Jan 2022 21:09:24 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Tue, 25 Jan 2022 21:09:24 +0100
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,
> Po Lu <luangruo@yahoo.com>,
> Philipp Stephani <phst@google.com>,
> emacs-devel@gnu.org
>
> > It is very worrisome that a change in glibc can break Emacs like that.
> > I wonder what it means for the maintainability of Emacs in the long
> > run. I have a bad feeling about this.
>
> Just to clarify this, nothing here has really broken Emacs. Emacs itself doesn't depend on libseccomp or the specific seccomp filter at all. It's just that newer versions of glibc will occasionally add new syscalls which will then need to get added to seccomp filters for sandboxing to continue working; the sandbox can only be secure if it fails-close (i.e. exits the process when encountering an unknown syscall).
That is exactly my problem with these situations: sandboxed Emacs
stops working too frequently for that to be a reliable option.
next prev parent reply other threads:[~2022-01-26 3:22 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 [this message]
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=834k5ri3jo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=p.stephani2@gmail.com \
--cc=phst@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.
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).