FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Device-mapper Development

 
 
LinkBack Thread Tools
 
Old 05-25-2012, 01:22 PM
Ondrej Kozina
 
Default Allow user w/o CAP_SYS_ADMIN to submit ioctl commands into DM

Hi,

I would like to post new version of my previous RFC with a set of changes for
device-mapper that would enable user w/o CAP_SYS_ADMIN capability to create
and manage his own devices.

Changes in version No. 2:
^^^^^^^^^^^^^^^^^^^^^^^^

(*) No major:minor translation to dentry (inode) in kernel space. Supposing
userspace should resolve that.

(*) Load time parameter to enable security enhancements

(*) Supposing security is enabled, userspace should handle open file descriptors
and kernel checks whether the user is authorised to access the device
linked to the device node.

The rest of message is the same as in original RFC

Simple use cases:
^^^^^^^^^^^^^^^^
(1) Non-root user would be able to create dm-crypt device from USB stick
(assuming the user has permission to access backing device)
(2) You can create pool of storage space for virtual machines. VM managers
would be able to administrate the pool w/o root permissions:

.--------------. .----------------.
|_owner: VM 01_| |__owner: VM 02__|
| |
| |
.---------------------------------.
|____owner: VM manager____________|

Short Overview:
^^^^^^^^^^^^^^
(1) The first checkpoint that decides whether the user has an access right to
submit ioctl cmds into DM driver are actually the attributes on dentry of
/dev/mapper/control (through general perm., ACL, LSM checks).

(2) After the DM_DEV_CREATE ioctl, new block device will receive FSUID and
from the context on behalf of which we entered into kernel

(3) Whenever user asks to manipulate DM device he must pass the test whether
he's the owner of DM device or he has CAP_FOWNER capability.

(4) During the table creation process we check whether the user has right to
READ/WRITE the backing device, according to table mode. For that purpose
I added a new function into target_type interface - dm_security_fn.

With regards
O.

Ondrej Kozina (3):
Adds support for user-submitted ioctl commands
Adds support for security checks in the linear target
Adds support for security checks in the crypt target

drivers/md/Makefile | 2 +-
drivers/md/dm-crypt.c | 18 +++++-
drivers/md/dm-ioctl.c | 141 +++++++++++++++++++++++++++++++++++------
drivers/md/dm-linear.c | 19 +++++-
drivers/md/dm-security.c | 95 +++++++++++++++++++++++++++
drivers/md/dm-sysfs.c | 15 +++++
drivers/md/dm-table.c | 23 +++++++-
drivers/md/dm.c | 87 +++++++++++++++++++++++++
drivers/md/dm.h | 12 ++++
include/linux/device-mapper.h | 5 ++
10 files changed, 393 insertions(+), 24 deletions(-)
create mode 100644 drivers/md/dm-security.c

--
1.7.8.6

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
 

Thread Tools




All times are GMT. The time now is 05:12 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org