From: Vito Caputo <vcaputo@pengaru.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question regarding blocking set[ug]id on processes including via suid executables
Date: Tue, 12 May 2020 03:44:08 -0700 [thread overview]
Message-ID: <20200512104408.jq3umt5hlqfbuhex@shells.gnugeneration.com> (raw)
In-Reply-To: <20200512094524.662gnls64rwjhct2@shells.gnugeneration.com>
On Tue, May 12, 2020 at 02:45:24AM -0700, Vito Caputo wrote:
> Hello folks,
>
> I'm curious if someone knows a way to do this using existing linux
> interfaces.
>
> I'd like to create a login lacking the ability to switch uid/gid.
>
> Even if the process has access to suid executables like /bin/su, and
> the user has the root password, I'd like the descendant processes of
> their login to be simply incapable of changing uid/gid, even when it's
> in the form of running a program w/suid bit set on an existing and
> accessible executable in the filesystem. No matter what, it just
> can't happen.
>
> Do we have any such thing today? I'd really like to be able to set
> this on a specific user and all logins of that user are simply stuck
> on that uid no matter what.
>
Basically what I'm looking for is a convention for login-time
application of the PR_SET_NO_NEW_PRIVS prctl, do we have anything
formalized in userspace for this? We've got NoNewPrivileges in
systemd but it's not really user-oriented AFAIK...
Maybe lkml isn't the right place to pose this question, any pointers
appreciated though.
Cheers,
Vito Caputo
next prev parent reply other threads:[~2020-05-12 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 9:45 Vito Caputo
2020-05-12 10:44 ` Vito Caputo [this message]
2020-05-12 11:30 ` Vito Caputo
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=20200512104408.jq3umt5hlqfbuhex@shells.gnugeneration.com \
--to=vcaputo@pengaru.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®