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

mount with priviledged port #15

Closed
GoogleCodeExporter opened this issue Jul 13, 2015 · 5 comments
Closed

mount with priviledged port #15

GoogleCodeExporter opened this issue Jul 13, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. have a NFS server that does not accept mount from unprivileged port
2. try to mount an exported device 

What is the expected output? What do you see instead?
- no error. Error on the .NET client.
"A string like umount request from 192.27.100.166 from unprivileged port" on 
the server 

What version of the product are you using? On what operating system?
.NET 4.0 on a windows 7 client SP1
freebsd server on other side

Please provide any additional information below.


Original issue reported on code.google.com by gras...@gmail.com on 17 Mar 2011 at 11:30

@GoogleCodeExporter
Copy link
Author

Hi,
can you try adding the insecure option in /etc/exports?

Original comment by mirko.ga...@gmail.com on 18 Mar 2011 at 5:43

@GoogleCodeExporter
Copy link
Author

Hi,
Yes if the remote paths are exported with insecure option the software will
mount it succesfully.
But with this method we lack of security.
There is no a method to specified that the client binding port can be
selected below the number 1024?

Many thanks
r.

Original comment by gras...@gmail.com on 21 Mar 2011 at 1:07

@GoogleCodeExporter
Copy link
Author

Hi,
this seems to be a limitation of the RPC library that I'm using. The previous 
version that used a managed implementation of RPC library can access also in 
secure mode. Try to use http://nekodrive.googlecode.com/files/NfsTestClient.zip 
to test it out. You may need visual c++ 2008 runtime.
I need time to investigate what's the difference between the two libraries but 
it takes time.. Anyway NFS v2 and v3 are not a secure protocols even without 
the "unsecure" flag as you probably know..

Original comment by mirko.ga...@gmail.com on 23 Mar 2011 at 5:37

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Original comment by mirko.ga...@gmail.com on 23 Mar 2011 at 5:38

@GoogleCodeExporter
Copy link
Author

Original comment by mirko.ga...@gmail.com on 30 May 2011 at 5:11

  • Changed state: Fixed

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

No branches or pull requests

1 participant