From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Nathan Dehnel <ncdehnel@gmail.com>
Cc: 39670@debbugs.gnu.org
Subject: bug#39670: Cannot mount NFS share as user or root
Date: Mon, 12 Oct 2020 23:22:36 -0400 [thread overview]
Message-ID: <87362i95dv.fsf@gmail.com> (raw)
In-Reply-To: <CAEEhgEux7QF4UAh+Jb7UQfWHOzrs72Jt4rEgiTDrqvULvZTrdw@mail.gmail.com> (Nathan Dehnel's message of "Fri, 2 Oct 2020 18:08:17 -0500")
Hello Nathan,
Nathan Dehnel <ncdehnel@gmail.com> writes:
> You should also setuid mount.nfs4 because the mount command calls that if
> you are using NFSv4.
[...]
I don't think that's necessary, if your program simply calls to the
'mount' command:
sudo strace -f -s200 mount localhost:/pub /tmp/pub
--8<---------------cut here---------------start------------->8---
[...]
[pid 19019] execve("/run/current-system/profile/sbin/mount.nfs", ["/run/current-system/profile/sbin/mount.nfs", "localhost:/pub", "/tmp/pub", "-o", "rw"], 0x7fff431b5038 /* 21 vars */) = 0
[...]
--8<---------------cut here---------------end--------------->8---
You see that mount ends up calling the mount.nfs binary, not mount.nfs4
(even though 'mount' reports this is using NFS v4.2).
If you have some software using mount.nfs4, that could be patched to
mount.nfs, as mount.nfs4 is just a symlink to mount.nfs.
Thanks,
Maxim
prev parent reply other threads:[~2020-10-13 3:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 1:08 Cannot mount NFS share as user or root Nathan Dehnel
2020-02-18 21:33 ` bug#39670: " Maxim Cournoyer
2020-02-18 21:43 ` Nathan Dehnel
2020-02-18 22:43 ` Maxim Cournoyer
2020-02-20 16:25 ` maxim.cournoyer
2020-05-28 3:11 ` Maxim Cournoyer
[not found] ` <CAEEhgEt109hcO1STeYv8rWT1hcn+K+JK-AO_1jvP6hJv8etf5w@mail.gmail.com>
[not found] ` <87y2kzvmc2.fsf@gmail.com>
[not found] ` <CAEEhgEtAeoxDcNQdR4BHx+9BCZq=9w5-A+Y0-J1L6Jf8rfFKkA@mail.gmail.com>
2020-09-25 1:53 ` Maxim Cournoyer
2020-10-01 19:49 ` Maxim Cournoyer
2020-10-02 23:08 ` Nathan Dehnel
2020-10-13 3:22 ` Maxim Cournoyer [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=87362i95dv.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=39670@debbugs.gnu.org \
--cc=ncdehnel@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.