From: Paul Moore <pmoore@redhat.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: libseccomp-discuss@lists.sourceforge.net,
Andy Lutomirski <luto@amacapital.net>,
linux-mips@linux-mips.org,
Markos Chandras <Markos.Chandras@imgtec.com>
Subject: Re: [libseccomp-discuss] [PATCH v3 0/2] Add support for MIPS BE/LE and O32 ABI
Date: Thu, 17 Apr 2014 16:30:08 -0400 [thread overview]
Message-ID: <34948662.6A7a6MXqdE@sifl> (raw)
In-Reply-To: <20140417200715.GA8190@linux-mips.org>
On Thursday, April 17, 2014 10:07:15 PM Ralf Baechle wrote:
> On Thu, Apr 17, 2014 at 12:38:36PM -0700, Andy Lutomirski wrote:
> > > For that reason I've long been contemplating to make syscalls of other
> > > ABIs unavailable, even without seccomp. Would that be useful for
> > > seccomp?
> >
> > It's still possible to execve something else.
>
> Would that other process then have a different syscall filter or is there
> only one global one?
Once a seccomp filter is loaded it is inherited by all child processes.
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2014-04-17 21:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1397550996-14805-1-git-send-email-markos.chandras@imgtec.com>
[not found] ` <1397738551.2725.18.camel@localhost>
[not found] ` <534FCF75.7060708@imgtec.com>
[not found] ` <4648181.no7KCQCtEi@sifl>
[not found] ` <534FFBCF.5010800@imgtec.com>
[not found] ` <1397750939.750.1.camel@localhost>
2014-04-17 16:20 ` [libseccomp-discuss] [PATCH v3 0/2] Add support for MIPS BE/LE and O32 ABI Andy Lutomirski
2014-04-17 16:24 ` Markos Chandras
2014-04-17 16:24 ` Markos Chandras
2014-04-17 19:13 ` Ralf Baechle
2014-04-17 19:38 ` Andy Lutomirski
2014-04-17 20:07 ` Ralf Baechle
2014-04-17 20:30 ` Paul Moore [this message]
2014-04-22 14:40 ` [PATCH 3.15] MIPS: Add new AUDIT_ARCH token for the N32 ABI on MIPS64 Markos Chandras
2014-04-22 14:40 ` Markos Chandras
2014-04-24 19:19 ` Paul Moore
2014-04-30 9:24 ` Markos Chandras
2014-04-30 9:24 ` Markos Chandras
2014-05-06 7:47 ` Markos Chandras
2014-05-06 7:47 ` Markos Chandras
2014-05-08 14:10 ` Paul Moore
2014-05-12 18:53 ` Paul Moore
2014-05-12 19:09 ` Eric Paris
2014-05-21 20:59 ` Paul Moore
2014-05-21 21:07 ` Andy Lutomirski
2014-05-21 22:10 ` James Hogan
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=34948662.6A7a6MXqdE@sifl \
--to=pmoore@redhat.com \
--cc=Markos.Chandras@imgtec.com \
--cc=libseccomp-discuss@lists.sourceforge.net \
--cc=linux-mips@linux-mips.org \
--cc=luto@amacapital.net \
--cc=ralf@linux-mips.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox