From: "Linda A. Walsh" <lvm@tlinx.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Bug! lvs shouldn't need 'root' access
Date: Tue, 12 Jul 2011 03:58:49 -0700 [thread overview]
Message-ID: <4E1C28E9.2020701@tlinx.org> (raw)
In-Reply-To: <20110710220815.GB7857@agk-dp.fab.redhat.com>
Alasdair G Kergon wrote:
> On Sun, Jul 10, 2011 at 10:40:13AM -0700, Linda A. Walsh wrote:
>
>> I could write to the darn things!, but all I NEED is read (hmmm
>>
>
> I thought so too when we first began work on LVM, but - surprising
> to me - there's been hardly any demand expressed for this feature.
>
> The proposed method of handling this was to accept dm ioctls on
> the actual devices themselves controlled by normal ioctl permissions.
>
> Currently, you need CAP_SYS_ADMIN (and access to /dev/mapper/control).
>
Ishtar:/suse/x86_64> filecap /sbin/lvm
file capabilities
/sbin/lvm sys_admin
Ishtar:/suse/x86_64> llg /dev/mapper/control
crw-rw---- 1 root disk 10, 236 Jul 8 16:52 /dev/mapper/control
(am in group disk).
---
Doesn't work. Still get access failures.
(open not permitted)
I got slightly further with cap_rawio, (gave more error messages).
I'm sure with enough experimenting, I could eventually find the
required set, but it seems to be a bit more than 1 cap.
Oh well, not that important...just found the caplibs on my system
and decided to give them a try...(didn't know the bins were
in yet!....only remember discussing their implementation about
11 years back. At least ACL's were faster...
(I made the exec +eip on the binary for sys_admin and rawio, and
that wasn't sufficient).
prev parent reply other threads:[~2011-07-12 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 17:40 [linux-lvm] Bug! lvs shouldn't need 'root' access Linda A. Walsh
2011-07-10 22:08 ` Alasdair G Kergon
2011-07-11 1:24 ` Linda A. Walsh
2011-07-11 2:24 ` Alasdair G Kergon
2011-07-11 2:31 ` Linda A. Walsh
2011-07-11 2:53 ` Alasdair G Kergon
2011-07-12 10:58 ` Linda A. Walsh [this message]
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=4E1C28E9.2020701@tlinx.org \
--to=lvm@tlinx.org \
--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 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.