From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Alan Third" <alan@idiocy.org>,
"Mattias Engdegård" <mattiase@acm.org>,
45198@debbugs.gnu.org, "Stefan Kangas" <stefankangas@gmail.com>,
"João Távora" <joaotavora@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Subject: bug#45198: 28.0.50; Sandbox mode
Date: Sun, 18 Apr 2021 11:11:28 +0200 [thread overview]
Message-ID: <CAArVCkThkE1iZwxOL78pJAzX2Vr8KxS9jn5dq1h_1DfS9+4LMQ@mail.gmail.com> (raw)
In-Reply-To: <83czusun95.fsf@gnu.org>
Am So., 18. Apr. 2021 um 08:21 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: Philipp <p.stephani2@gmail.com>
> > Date: Sat, 17 Apr 2021 21:52:59 +0200
> > Cc: Mattias Engdegård <mattiase@acm.org>,
> > João Távora <joaotavora@gmail.com>,
> > 45198@debbugs.gnu.org,
> > stefankangas@gmail.com,
> > monnier@iro.umontreal.ca,
> > alan@idiocy.org
> >
> > > So you are going to suggest that we rely on some auditing of the
> > > syscalls Emacs uses now to decide which ones to filter and which not?
> >
> > I don't mean that we should wade through all potential syscalls that Emacs could make. Typically you can come up with such a Seccomp policy iteratively: run Seccomp in advisory mode (i.e. only log syscalls), then allow the syscalls that are both necessary and harmless in the policy.
>
> Emacs can be invoked to do many different things, and will
> correspondingly present very different profiles of syscalls. Is the
> procedure you envision practical, let alone seamless, given that it
> will have to become part of the maintenance and the release process?
Yes. There aren't that many syscalls to begin with, and Emacs uses
only a small subset of them. New Emacs or libc versions occasionally
introduce new syscalls, but finding and allowing them tends to be not
that big of a deal.
> > > And what about users who make local changes
> > > in their Emacs?
> >
> > They can provide their own Seccomp policies or modify the ones included in Emacs.
>
> What does providing a policy entail? can you describe the procedure of
> tailoring a policy to changes in the Emacs code?
1. Run the Emacs sandbox with the code you want to run.
2. Emacs will crash with SIGSYS if it hits a forbidden/unknown
syscall. Ensure that this generates a coredump.
3. Check the backtrace for the coredump (e.g. coredumpctl debug)
and/or the Seccomp audit logs (ausearch) for the syscall that
triggered the signal.
4. Add a rule for the syscall and its arguments to the BPF generation
program, e.g. lib-src/seccom-filter.c.
5. Regenerate the BPF rule file.
next prev parent reply other threads:[~2021-04-18 9:11 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 18:01 bug#45198: 28.0.50; Sandbox mode Stefan Monnier
2020-12-12 19:48 ` Eli Zaretskii
2020-12-12 21:06 ` Stefan Monnier
2020-12-13 3:29 ` Eli Zaretskii
2020-12-13 4:25 ` Stefan Monnier
2020-12-13 11:14 ` João Távora
2020-12-13 17:07 ` Philipp Stephani
2020-12-13 15:31 ` Mattias Engdegård
2020-12-13 17:09 ` Philipp Stephani
2020-12-13 17:04 ` Philipp Stephani
2020-12-13 17:57 ` Stefan Monnier
2020-12-13 18:13 ` Philipp Stephani
2020-12-13 18:43 ` Stefan Monnier
2020-12-14 11:05 ` Philipp Stephani
2020-12-14 14:44 ` Stefan Monnier
2020-12-14 15:37 ` Philipp Stephani
2020-12-19 22:41 ` Philipp Stephani
2020-12-19 23:16 ` Stefan Monnier
2020-12-20 12:28 ` Philipp Stephani
2020-12-22 10:57 ` Philipp Stephani
2020-12-22 14:43 ` Stefan Monnier
2020-12-19 18:18 ` Philipp Stephani
2021-04-10 17:44 ` Philipp Stephani
2020-12-19 22:22 ` Philipp Stephani
2020-12-20 15:09 ` Eli Zaretskii
2020-12-20 18:14 ` Philipp Stephani
2020-12-20 18:29 ` Eli Zaretskii
2020-12-20 18:39 ` Philipp Stephani
2020-12-29 13:50 ` Philipp Stephani
2020-12-29 15:43 ` Eli Zaretskii
2020-12-29 16:05 ` Philipp Stephani
2020-12-29 17:09 ` Eli Zaretskii
2020-12-31 15:05 ` Philipp Stephani
2020-12-31 16:50 ` Eli Zaretskii
2021-04-10 19:11 ` Philipp Stephani
2020-12-13 18:52 ` Stefan Monnier
2020-12-13 20:13 ` João Távora
2020-12-14 11:12 ` Mattias Engdegård
2020-12-14 13:44 ` Philipp Stephani
2020-12-14 14:48 ` Stefan Monnier
2020-12-14 15:59 ` Mattias Engdegård
2020-12-17 13:08 ` Philipp Stephani
2020-12-17 17:55 ` Mattias Engdegård
2020-12-18 15:21 ` Philipp Stephani
2020-12-18 18:50 ` Mattias Engdegård
2020-12-19 15:08 ` Philipp Stephani
2020-12-19 17:19 ` Mattias Engdegård
2020-12-19 18:11 ` Stefan Monnier
2020-12-19 18:46 ` Mattias Engdegård
2020-12-19 19:48 ` João Távora
2020-12-19 21:01 ` Stefan Monnier
2020-12-20 13:15 ` Mattias Engdegård
2020-12-20 14:02 ` Stefan Monnier
2020-12-20 14:12 ` Mattias Engdegård
2020-12-20 15:08 ` Stefan Monnier
2020-12-22 11:12 ` Philipp Stephani
2020-12-28 8:23 ` Stefan Kangas
2020-12-29 13:58 ` Philipp Stephani
2020-12-30 14:59 ` Mattias Engdegård
2020-12-30 15:36 ` Alan Third
2021-04-17 15:26 ` Mattias Engdegård
2021-04-17 15:44 ` Philipp
2021-04-17 15:57 ` Eli Zaretskii
2021-04-17 16:10 ` Philipp
2021-04-17 16:15 ` Eli Zaretskii
2021-04-17 16:19 ` Eli Zaretskii
2021-04-17 16:20 ` Philipp Stephani
2021-04-17 16:33 ` Eli Zaretskii
2021-04-17 19:14 ` Philipp Stephani
2021-04-17 19:23 ` Eli Zaretskii
2021-04-17 19:52 ` Philipp
2021-04-18 6:20 ` Eli Zaretskii
2021-04-18 9:11 ` Philipp Stephani [this message]
2021-04-18 9:23 ` Eli Zaretskii
2021-04-17 17:48 ` Mattias Engdegård
2021-04-17 18:21 ` Stefan Monnier
2021-04-17 18:59 ` Mattias Engdegård
2021-04-17 19:42 ` Philipp
2021-04-17 19:57 ` Alan Third
2021-04-19 15:41 ` Mattias Engdegård
2021-04-17 19:19 ` Philipp Stephani
2021-04-17 17:22 ` Mattias Engdegård
2021-04-17 17:57 ` Stefan Monnier
2021-04-17 19:21 ` Philipp Stephani
2021-04-17 19:16 ` Philipp Stephani
2021-04-17 16:58 ` Stefan Monnier
2021-04-17 17:14 ` Eli Zaretskii
2021-04-17 17:53 ` Stefan Monnier
2021-04-17 18:15 ` Eli Zaretskii
2021-04-17 18:47 ` Stefan Monnier
2021-04-17 19:14 ` Eli Zaretskii
2021-04-17 20:26 ` Stefan Monnier
2021-04-18 6:24 ` Eli Zaretskii
2021-04-18 14:25 ` Stefan Monnier
2021-07-05 19:12 ` Philipp
2021-09-17 12:13 ` Mattias Engdegård
2021-09-17 13:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-17 19:49 ` Mattias Engdegård
2022-09-11 11:28 ` Lars Ingebrigtsen
2022-09-13 12:37 ` mattiase
2022-09-13 12:53 ` João Távora
2022-09-13 13:02 ` João Távora
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=CAArVCkThkE1iZwxOL78pJAzX2Vr8KxS9jn5dq1h_1DfS9+4LMQ@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=45198@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@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).