From: Andreas Hasenack <andreas@canonical.com>
To: Linux-audit@redhat.com
Subject: Current problematic cases with immutable loginuid
Date: Mon, 7 Jun 2021 12:09:45 -0300 [thread overview]
Message-ID: <CANYNYEFw4qj_q5Q+bSVKsAFXY6mb_6r7rfd=W8TF4QLkuvuw5g@mail.gmail.com> (raw)
Hi,
I was reading up on setting loginuid immutable, and was wondering what
are the current known problematic cases.
In general, anything that requires switching a set loginuid to another
value will be blocked:
- sshd started on another port by the logged in user to debug
something, and that debug requires logging in as a different user than
the one who started it up
- container that starts up within the user's session, instead of via
dockerd/containerd, systemd, or some other already-running daemon. I
read a lengthy bug in Redhat's bugzilla about a bad interaction with
systemd's nspawn, where apparently the container is started directly,
and thus inheriting the user's loginuid, instead of being started via
a request to systemd (the daemon)
The manpage mentions "certain kinds of containers", and I assume it's
a reference to nspawn's case above.
Are there other prominent problematic situations that people have
encountered while setting loginuid immutable?
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next reply other threads:[~2021-06-07 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 15:09 Andreas Hasenack [this message]
2021-06-07 17:49 ` Current problematic cases with immutable loginuid Richard Guy Briggs
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='CANYNYEFw4qj_q5Q+bSVKsAFXY6mb_6r7rfd=W8TF4QLkuvuw5g@mail.gmail.com' \
--to=andreas@canonical.com \
--cc=Linux-audit@redhat.com \
/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.