From: "Jan Luebbe" <jlu@pengutronix.de>
To: "Ross Burton" <ross.burton@intel.com>,
"Khem Raj" <raj.khem@gmail.com>,
"Martin Hundebøll" <martin@geanix.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Enrico Jorns <ejo@pengutronix.de>
Subject: Re: [OE-core] [PATCH] file: explicitly disable seccomp
Date: Tue, 31 Mar 2020 12:57:56 +0200 [thread overview]
Message-ID: <9464fbdc93aa48aac796a3ea44e04efcd9564963.camel@pengutronix.de> (raw)
In-Reply-To: <f6cb669c-d302-c1fa-e2ed-5995b82677ed@intel.com>
Hi,
On Mon, 2020-01-20 at 17:10 +0000, Ross Burton wrote:
> On 20/01/2020 15:45, Khem Raj wrote:
> > pseudo needs some love since it alters syscalls which go out of bounds
> > what is allowed by libseccomp until then pin your file version to 5.37
> > in arch till a supported distro is affected by same problem. It wont
> > be long better option is to fix pseudo
>
> That's not quite right. pseudo LD_PRELOADs itself into file, and makes
> syscalls which are not whitelisted in file's seccomp configuration.
>
> There's nothing pseudo can do to solve this.
I stumbled across this thread when checking why libseccomp is not in
oe-core or meta-oe. It seems to me that pseudo could intercept the
seccomp(2) or libseccomps seccomp_* function calls and report them as
unsupported to simulate running on a kernel without seccomp support.
What am I missing? :)
Regards,
Jan
next prev parent reply other threads:[~2020-03-31 10:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 11:28 [PATCH] file: explicitly disable seccomp Ross Burton
2019-10-18 12:33 ` Khem Raj
2019-10-18 21:28 ` Richard Purdie
2019-10-19 5:26 ` Khem Raj
2020-01-20 12:53 ` Martin Hundebøll
2020-01-20 15:45 ` Khem Raj
2020-01-20 17:10 ` Ross Burton
2020-01-20 18:53 ` Khem Raj
2020-03-31 10:57 ` Jan Luebbe [this message]
2020-03-31 11:04 ` [OE-core] " Richard Purdie
2020-04-03 13:36 ` Richard Purdie
2020-04-03 14:23 ` Khem Raj
2020-04-03 17:53 ` Richard Purdie
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=9464fbdc93aa48aac796a3ea44e04efcd9564963.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=ejo@pengutronix.de \
--cc=martin@geanix.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross.burton@intel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox