From: "Stuart D. Gathman" <stuart@gathman.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>
Subject: Re: [linux-lvm] lvcreate from a setuid-root binary
Date: Fri, 16 Nov 2018 10:41:53 -0500 [thread overview]
Message-ID: <1542382913.30686.3@mail.gathman.org> (raw)
In-Reply-To: <2a7f4f1fc1a54fd6eca7d7bc9a6249ae@cs.uni-dortmund.de>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
It's not very elegant, but the quick and dirty solution is to use sudo
to allow certain users to run specific commands with a real uid of
root. You can say exactly what arguments the user has to use - the
sudoers file is where this is configured. Or you can make a script -
which is probably better. But said script should have no arguments, or
as few as possible - because any complexity allows that user to attempt
to exploit it to acheive root. Such a script could trivially bring a
specific LV online, writable by a specific user. More complex
requirement would be - more complex.
If LVM has more elegant features for this kind of thing, I'm all ears.
On Fri, Nov 16, 2018 at 8:43 AM, Christoph Pleger
<christoph.pleger@cs.uni-dortmund.de> wrote:
>> Go back to the beginning and describe the original problem you are
>> trying to solve and the constraints you have and ask for advice about
>> ways to achieve it.
>
> The beginning is that I want to create a user-specific logical volume
> when a user logs in to a service that authenticates its users through
> pam and that does not run as root.
>
> Regards
> Christoph
>
[-- Attachment #2: Type: text/html, Size: 1386 bytes --]
next prev parent reply other threads:[~2018-11-16 15:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 16:39 [linux-lvm] lvcreate from a setuid-root binary Christoph Pleger
2018-11-15 17:57 ` Alasdair G Kergon
2018-11-16 13:43 ` Christoph Pleger
2018-11-16 15:32 ` Zdenek Kabelac
2018-11-16 16:12 ` Christoph Pleger
2018-11-16 17:21 ` Roger Heflin
2018-11-16 15:41 ` Stuart D. Gathman [this message]
2018-11-21 9:56 ` Christoph Pleger
2018-11-21 9:58 ` Vladislav Bogdanov
2018-11-21 10:23 ` Christoph Pleger
2018-11-17 0:24 ` Alasdair G Kergon
2018-11-19 8:55 ` Christoph Pleger
2018-11-19 13:01 ` Alasdair G Kergon
2018-11-19 13:19 ` Bryn M. Reeves
2018-11-19 15:17 ` Christoph Pleger
2018-11-19 15:35 ` Christoph Pleger
[not found] <1044845531.2858991.1542636286779.ref@mail.yahoo.com>
2018-11-19 14:04 ` matthew patton
2018-11-19 15:03 ` Christoph Pleger
[not found] <1479542688.2901829.1542643514135.ref@mail.yahoo.com>
2018-11-19 16:05 ` matthew patton
[not found] <1657965510.4711397.1542904883060.ref@mail.yahoo.com>
2018-11-22 16:41 ` matthew patton
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=1542382913.30686.3@mail.gathman.org \
--to=stuart@gathman.org \
--cc=agk@redhat.com \
--cc=linux-lvm@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 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).