From: Henrik Grindal Bakken <hgb@ifi.uio.no>
To: Chris PeBenito <pebenito@ieee.org>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: [RFC] files: Make files_{relabel,manage}_non_security_types work on all file types
Date: Wed, 22 Jan 2020 21:24:01 +0100 [thread overview]
Message-ID: <87sgk78cke.fsf@cisco.com> (raw)
In-Reply-To: <068afebc-bee1-0d1e-ed37-e1473f66f982@ieee.org> (Chris PeBenito's message of "Wed, 22 Jan 2020 05:03:06 -0500")
Chris PeBenito <pebenito@ieee.org> writes:
> On 1/21/20 9:06 AM, Henrik Grindal Bakken wrote:
>
>> Ok. Then I would recomment rewriting the systemd_tmpfiles_t rules a
>> bit, because today it has a serious amount of AVC violations for pretty
>> standard usage.
>
> Perhaps. However, it depends on what you consider standard usage.
I suppose. It might not be standard out-of-the-distro-box, but it
supports managing all of these classes of files, and I would've
preferred my policy to support that.
>> There are no matching interfaces for lnk_files, at least. Any
>> suggestions as to how to set up the tmpfiles rules?
>
> By adding new interfaces that are like the existing
> files_manage_non_security_files() interface, but for lnk_file.
Ok. Is there interest in a patch for that, or should I just conjure up
something locally that works for me?
--
Henrik Grindal Bakken <hgb@ifi.uio.no>
PGP ID: 8D436E52
Fingerprint: 131D 9590 F0CF 47EF 7963 02AF 9236 D25A 8D43 6E52
next prev parent reply other threads:[~2020-01-22 20:24 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
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 [this message]
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=87sgk78cke.fsf@cisco.com \
--to=hgb@ifi.uio.no \
--cc=pebenito@ieee.org \
--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).