selinux-refpolicy.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Grindal Bakken <hgb@ifi.uio.no>
To: <selinux-refpolicy@vger.kernel.org>
Subject: Re: [RFC] files: Make files_{relabel,manage}_non_security_types work on all file types
Date: Sat, 18 Jan 2020 08:11:02 +0100	[thread overview]
Message-ID: <87v9p99r3t.fsf@cisco.com> (raw)
In-Reply-To: <20200117231500.59904-1-hgb@ifi.uio.no> (Henrik Grindal Bakken's message of "Sat, 18 Jan 2020 00:15:00 +0100")

Henrik Grindal Bakken <hgb@ifi.uio.no> writes:

> From: Henrik Grindal Bakken <henribak@cisco.com>
>
> This is the same behavious as files_*_non_auth_types have.

The rationale for changing this is that the systemd-tmpfiles rules use
files_manage_non_security_files() (and ..._relabel_...), which doesn't
work well if you use tmpfiles for somewhat more exotic paths that the
standard setup.

An alternative to this approach is to change the rules in systemd.te for
systemd_tmpfiles_t, but it seems to me like this change would be more in
line with what's done for the similar interfaces.

-- 
Henrik Grindal Bakken <hgb@ifi.uio.no>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963  02AF 9236 D25A 8D43 6E52

  reply	other threads:[~2020-01-18  7:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 23:15 [RFC] files: Make files_{relabel,manage}_non_security_types work on all file types Henrik Grindal Bakken
2020-01-18  7:11 ` Henrik Grindal Bakken [this message]
2020-01-21 13:36 ` Chris PeBenito
2020-01-21 14:06   ` Henrik Grindal Bakken
2020-01-22 10:03     ` Chris PeBenito
2020-01-22 20:24       ` Henrik Grindal Bakken
2020-02-08 14:49         ` Chris PeBenito

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=87v9p99r3t.fsf@cisco.com \
    --to=hgb@ifi.uio.no \
    --cc=selinux-refpolicy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).