Ubuntu – NFS with encrypted ubuntu home directory

nfspuppetUbuntuubuntu-12.04vagrant

I am having trouble getting NFS setup on with vagrant:

On my local machine I have installed NFS:

apt-get install nfs-common nfs-kernel-server

And in my Vagrantfile set it to be used:

config.vm.share_folder("v-root", "/vagrant", ".", :nfs => true)

On vagrant up I get:

exportfs: /home/<user>/path/to/dir does not support NFS export

Mounting NFS shared folders failed. This is most often caused by the NFS
client software not being installed on the guest machine. Please verify
that the NFS client software is properly installed, and consult any resources
specific to the linux distro you're using for more information on how to
do this.

Am I missing a step or two here?

I'm aware of some issues with ubuntus encrypted home folders and NFS but I understand this is only meant to be a problem before boot.

[update] my /etc/exports file looks like this:

# VAGRANT-BEGIN: 5af3e5d6-b086-416d-8eab-987275445634
/home/<user>/path/to/dir 192.168.33.11(rw,no_subtree_check,all_squash,
anonuid=1000,anongid=1000,fsid$
# VAGRANT-END: 5af3e5d6-b086-416d-8eab-987275445634

Best Answer

Actually is not possibile to export anything via NFS inside an ecryptfs volume. exportfs: Warning: /home/user/share does not support NFS export

Related Solutions

Ubuntu – Clients with home directories on NFS hanging on login

I have seen this kind of behavior when a directory in the PATH is automounted nfs and that directory is unavailable or unresponsive.

I would check the PATH for those accounts. Make sure there is nothing automounted in the path. Then you can add directories one by one and find out which causes the hang.

Another possibility is that you may have some uid mismatch between your accounts from samba and your accounts on the nfs server. When you run 'ls -l' on a users nfs home directory, do you see the correct username? If not you will need to configure Samba to map the usernames to the uids that the nfs server is using.

Linux – NFS. Non-root mount requests

The most likely reason you are having problems with non-root mounts is the "secure" export option, which is on by default. It disallows mount requests that come in with a source port greater than 1024. On most systems, binding to a port less than 1024 requires root access, so this is a fairly decent way of ensuring the mount was made by root.

The issue, as explained in the README for my NfSpy penetration testing tool, is that the NFS protocol (versions 2, 3, and even 4, without proper configuration) completely trusts the user ID sent in requests from client machines. By limiting requests to only those made by root, you limit your trust to only users on the client machine who have root access. Without this setting (using "insecure" in your exports file), any user can claim to have any UID and access any file on the export.

The reason it is working on Linux is probably because /bin/mount is setuid root:

~$ ls -l /bin/mount
-rwsr-xr-x 1 root root 72188 2011-01-20 13:54 /bin/mount

Just a hunch, but check the permissions on the mount binary on your FreeBSD system. If it is setuid, then you still have a problem, and I don't know what it is. If not, then that would explain what's going on.

Good luck with this, but please consider the security implications of allowing any user on a system to access any file on your server. I recommend using NFS4 with GSS authentication mechanisms instead of the traditional AUTH_SYS flavor.

Related Topic