From: Steve French <smfrench@austin.rr.com>
To: linux-fsdevel@vger.kernel.org
Subject: Should a non-root user always be able to mount on a directory they do not own if /etc/fstab entry is marked "user"
Date: Thu, 24 Nov 2005 20:11:49 -0600 [thread overview]
Message-ID: <438672E5.1080202@austin.rr.com> (raw)
Should a non-root user always be able to mount on a directory they do
not own if /etc/fstab entry is marked "user"? Are there other
restrictions that I should check?
In particular, bug
https://bugzilla.samba.org/show_bug.cgi?id=1617
asks the cifs vfs allow that a user can mount over a directory owned by
root if /etc/fstab says "user" on the matching line.
If there are not other security problems, I was planning to follow the
suggestion in the bug? I noticed that at least for this version of
SuSE smbfs no longer can do setuid mounts, so I could not compare with
that, but presumably nfs has no particular security checks in mount
beyond what is already there in mount.cifs.c (with the suggested
modification)
next reply other threads:[~2005-11-25 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 2:11 Steve French [this message]
2005-11-29 20:18 ` Should a non-root user always be able to mount on a directory they do not own if /etc/fstab entry is marked "user" Dave Kleikamp
2005-11-29 20:51 ` Steve French
2005-11-29 21:55 ` Dave Kleikamp
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=438672E5.1080202@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-fsdevel@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