GNU bug report logs - #56359
seccomp test failures on RHEL 9.0

Previous Next

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: "Basil L. Contovounesios" <contovob <at> tcd.ie>, Glenn Morris <rgm <at> gnu.org>, Philipp Stephani <p.stephani2 <at> gmail.com>, 56359 <at> debbugs.gnu.org
Subject: bug#56359: seccomp test failures on RHEL 9.0
Date: Tue, 11 Oct 2022 21:47:28 +0200

Paul Eggert <eggert <at> cs.ucla.edu> writes:

> My "fix" involved allowing all uses of clone3, which (as Philipp noted
> in August) is problematic. I'm not sure what's being tested for, but
> if clone3 lets you evade the checks then the test is arguably more
> trouble than it's worth. Would marking it as :unstable lessen the
> number of false alarms we're getting? If not, perhaps we should remove
> it or mark it as :dont-use-unless-you-know-what-youre-doing or
> whatever.

And pidfd_open also sounds like a non-safe call (without looking at it
closely).

Skimming the tests, they seem to test pretty basic functionality in the
seccomp area -- that is, without allowing pidfd_open/clone3, nothing
will be able to run using the seccomp functionality.  But since those
are somewhat unsafe, then...  what's the point?

But I may be missing how this is supposed to be used altogether.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.