From: Russell Coker <russell@coker.com.au>
To: selinux-refpolicy@vger.kernel.org
Subject: /run/credentials
Date: Fri, 10 Jul 2026 19:29:31 +1000 [thread overview]
Message-ID: <2526945.QCnGb9OGeP@dojacat> (raw)
Does anyone have any policy for credentials?
Below is what I'm getting on my systems running Debian/Testing, directories
like the following with no files in them.
# find /run/credentials/
/run/credentials/
/run/credentials/getty@tty2.service
/run/credentials/systemd-resolved.service
/run/credentials/systemd-journald.service
# find /run/credentials/ -type f
#
Currently what is happening is daemons trying to read their own dir and being
denied, here's an example:
type=AVC msg=audit(1783593117.796:143): avc: denied { open } for pid=1034
comm="agetty" path="/run/credentials/getty@tty1.service" dev="tmpfs" ino=1
scontext=system_u:system_r:getty_t:s0 tcontext=system_u:object_r:tmpfs_t:s0
tclass=dir permissive=1
I was thinking of adding a credentials_runtime_t type and labelling everything
under /run/credentials with it, giving daemons read-access to directories and
wait to write real policy until people make daemons actually use it.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next reply other threads:[~2026-07-10 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 9:29 Russell Coker [this message]
2026-07-10 10:04 ` /run/credentials 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=2526945.QCnGb9OGeP@dojacat \
--to=russell@coker.com.au \
--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