Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nfs_mount.exe can fail if the server does not use 'insecure' export option #13

Open
cedricblancher opened this issue Nov 10, 2023 · 2 comments

Comments

@cedricblancher
Copy link
Contributor

nfs_mount.exe can fail if the server does not use 'insecure' export option. It seems the Windows nfs client always has send RPC requests from a TCP port < 1024.

@smx-smx
Copy link

smx-smx commented Nov 18, 2023

Can confirm. The mount command must be ran as the unprivileged user, in order to place the network drive in the same user namespace (or the network share would only be accessible by Administrator). This however means the mount command will use a high port (>1024) which is deemed insecure and rejected by the server. The error isn't obvious (points to a generic getent permission denial).

@gisburn
Copy link
Contributor

gisburn commented Jun 19, 2024

This bug is fixed since bc28985

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants