From: Gionatan Danti <g.danti@assyoma.it>
To: Dominick Grift <dominick.grift@defensec.nl>
Cc: "Christian Göttsche" <cgzones@googlemail.com>, selinux@vger.kernel.org
Subject: Re: lnk_file read permission
Date: Fri, 31 Jul 2020 19:09:51 +0200 [thread overview]
Message-ID: <9f363af014b8670267af982f9d4a6362@assyoma.it> (raw)
In-Reply-To: <ypjld04bmxry.fsf@defensec.nl>
Il 2020-07-31 18:53 Dominick Grift ha scritto:
> I agree with this, also for compatibility with systemds'
> StateDirectory=
> in conjunction with DynamicUsers=.
>
> I you would for example have a mysqld service with
> StateDirectory=mysqld
> and DynamicUser=yes then systemd would maintain a symlink
> /var/lib/mysqld that points to /var/lib/private/mysqld
>
> Even if you do not use that functionality it should still be compatible
> with /data/lib /var/lib equivalency.
>
> I do this consistently in my personal policy. ie instead of using
> "/var/lib/mysqld(/.*)? i use /var/lib/mysqld -d and /var/lib/mysqld/.*
> so that the symlink context stay's generic
>
> Regardless, this is a policy design issue that you should probably take
> to your distribution maintainer.
I did not know that systemd would, with specific settings, create a
private mysql data dir.
I would try the var_lib_t approach more widely.
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2020-07-31 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 9:57 lnk_file read permission Gionatan Danti
2020-07-31 13:12 ` Stephen Smalley
2020-07-31 16:56 ` Gionatan Danti
2020-07-31 16:25 ` Christian Göttsche
2020-07-31 16:53 ` Dominick Grift
2020-07-31 17:09 ` Gionatan Danti [this message]
2020-07-31 19:37 ` Gionatan Danti
2020-07-31 19:44 ` Dominick Grift
2020-07-31 19:49 ` Gionatan Danti
2020-07-31 17:00 ` Gionatan Danti
2020-07-31 17:45 ` Dominick Grift
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=9f363af014b8670267af982f9d4a6362@assyoma.it \
--to=g.danti@assyoma.it \
--cc=cgzones@googlemail.com \
--cc=dominick.grift@defensec.nl \
--cc=selinux@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).