From: "Mantas Mikulėnas" <grawity@gmail.com>
To: util-linux@vger.kernel.org
Subject: Re: RFC: usermount - a secure mount for unpriviledged users
Date: Wed, 18 Nov 2015 20:24:19 +0200 [thread overview]
Message-ID: <564CC253.2080301@gmail.com> (raw)
In-Reply-To: <n2ibqp$ui6$1@ger.gmane.org>
On 2015-11-18 19:17, U.Mutlu wrote:
> Currently no responsible admin can grant permission to the mount pgm
> to his users, because of the dangers inherent with bind-mounting etc.
>
> I suggest there should be an additional mount program destined for
> unpriviledged users (to be used via sudo).
>
> It should be a stripped down version of the mount pgm, with only some
> basic options for mounting, but without the dangerous options like
> bind-mount.
>
> The new program should of course have a different name, for example
> "usermount".
>
> I think this is the most clean solution to this problem.
>
> Users are intessted in mounting their own filesystems into
> their own mountpoints, ie. they don't neccesserily need fstab or mtab etc.:
> $ mkdir mymnt1 mymnt2
> $ sudo usermount myfs.img ./mymnt1
> $ sudo usermount my.iso ./mymnt2
fwiw, udisks2 already lets you mount removable drives and loop devices
under (/run)/media:
$ udisksctl mount -b /dev/sdb4
$ udisksctl loop-setup -f ~/foo.img
--
Mantas Mikulėnas <grawity@gmail.com>
next prev parent reply other threads:[~2015-11-18 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 17:17 RFC: usermount - a secure mount for unpriviledged users U.Mutlu
2015-11-18 18:24 ` Mantas Mikulėnas [this message]
2015-11-19 0:53 ` mount-user.c U.Mutlu
2015-12-03 20:06 ` mount-user.c Michael Conrad
2015-12-04 7:32 ` mount-user.c U.Mutlu
2015-11-19 1:08 ` RFC: usermount - a secure mount for unpriviledged users Casper Ti. Vector
2015-11-19 1:53 ` udevil - mount tool U.Mutlu
2015-11-19 2:21 ` Casper Ti. Vector
2015-11-19 11:05 ` RFC: usermount - a secure mount for unpriviledged users Karel Zak
2015-11-19 18:07 ` U.Mutlu
2015-11-19 18:18 ` U.Mutlu
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=564CC253.2080301@gmail.com \
--to=grawity@gmail.com \
--cc=util-linux@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