From: Dominick Grift <dac.override@gmail.com>
To: Dan Noland <dan@starlab.io>
Cc: "selinux-refpolicy@vger.kernel.org" <selinux-refpolicy@vger.kernel.org>
Subject: Re: fs_use_xattr question
Date: Sat, 15 Jun 2019 13:42:40 +0200 [thread overview]
Message-ID: <20190615114240.GA2929@brutus.lan> (raw)
In-Reply-To: <20190614220149.GE18841@starlab.io>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Fri, Jun 14, 2019 at 10:01:52PM +0000, Dan Noland wrote:
> - Hello -
>
> I have a custom stacked filesystem and I was having difficulty with
> security xattrs. I traced it back to missing:
>
> fs_use_xattr myfs gen_context(system_u:object_r:fs_t,s0);
>
> Which works nicely when I rebuild/reinstall the base policy. However
> some experimentation and checking of old mailing posts seems to
> indicate that it is not possible to achieve this in a policy module.
>
> Because my FS is stacked I would be perfectly happy just to
> inherit whatever the fs_use_xattr state of my lower filesystem is.
>
> Is there a best practice for achieving this or do I need to always
> rebuild the base policy?
If you are able to use CIL then you might be able to do this:
echo '(fsuse xattr "myfs" (system_u object_r fs_t ((s0)(s0))))' > mytest.cil && sudo semodule -i mytest.cil
>
> Thank you for your time.
>
> --
> TY,
> Dan Noland
--
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2019-06-15 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 22:01 fs_use_xattr question Dan Noland
2019-06-15 11:42 ` Dominick Grift [this message]
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=20190615114240.GA2929@brutus.lan \
--to=dac.override@gmail.com \
--cc=dan@starlab.io \
--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 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.