All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Jeremy Sowden <jeremy@azazel.net>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: Re: iptables & nftables secmark unit-tests
Date: Wed, 20 Nov 2024 13:29:25 +0100	[thread overview]
Message-ID: <Zz3WJSUIW0ds-5W9@orbyte.nwl.cc> (raw)
In-Reply-To: <20241119224608.GD3017153@celephais.dreamlands>

Hi Jeremy,

On Tue, Nov 19, 2024 at 10:46:08PM +0000, Jeremy Sowden wrote:
> When running the test-suites for iptables and nftables, the secmark
> tests usually fail 'cause I don't have selinux installed and configured,
> and I ignore them.  However, I want to get the test-suites working with
> Debian's CI, so any pointers for how I need to set up selinux would be
> gratefully received.

That's odd, my VM for testing doesn't run selinux and the testsuites
still pass. The only thing I see is selinux support in the kernel
config:

CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS=9
CONFIG_SECURITY_SELINUX_SID2STR_CACHE_SIZE=256
CONFIG_DEFAULT_SECURITY_SELINUX=y
CONFIG_LSM="yama,loadpin,safesetid,integrity,selinux,smack,tomoyo,apparmor"

SELinux-ignorant as I am, I wasn't able to find a place which defines
selinux contexts/policies, no idea how the kernel validates the
'system_u:object_r:firewalld_exec_t:s0' used for iptables SECMARK
testing for instance. All I can tell is that we had to change this for
testing on RHEL.

HTH, Phil

  reply	other threads:[~2024-11-20 12:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 22:46 iptables & nftables secmark unit-tests Jeremy Sowden
2024-11-20 12:29 ` Phil Sutter [this message]
2024-11-21 10:33   ` Jeremy Sowden

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=Zz3WJSUIW0ds-5W9@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=jeremy@azazel.net \
    --cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.