From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Robert Frohl <rfrohl@suse.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [PATCH] Revert "dns-hatchet: apply resolv.conf's selinux context to new resolv.conf"
Date: Fri, 12 Jun 2026 19:04:47 +0200 [thread overview]
Message-ID: <aiw8L3XwjibHS2_-@zx2c4.com> (raw)
In-Reply-To: <20260608133610.108416-1-rfrohl@suse.com>
On Mon, Jun 08, 2026 at 03:36:10PM +0200, Robert Frohl wrote:
> This reverts commit 2ce4680bd34f371aacd3c09673c3c907274321cd.
>
> selinux does not allow every domain to set file contexts and will raise
> relabelto/relabelfrom AVCs and block these changes if a domain tries to update
> the selinux context.
>
> It is better to ignore selinux and leave the proper labeling to the
> selinux policy, which can add proper file transitions for the right
> context.
Does any existent selinux policy have anything to handle this? Or is this
purely speculative/future-facing?
Also, wondering if any distros are still shipping the hatchet.
next prev parent reply other threads:[~2026-06-12 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 13:36 [PATCH] Revert "dns-hatchet: apply resolv.conf's selinux context to new resolv.conf" Robert Frohl
2026-06-12 17:04 ` Jason A. Donenfeld [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-24 9:33 Robert Frohl
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=aiw8L3XwjibHS2_-@zx2c4.com \
--to=jason@zx2c4.com \
--cc=rfrohl@suse.com \
--cc=wireguard@lists.zx2c4.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