[PATCH 0/1] Remote calls don't need to use privilege ports

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Over the weekend I did some experimenting with
the remote call code in rpcbind. The code does 
functionally work but is very antiquated when
it comes to the latest NFS versions. 

Since only UDP sockets are used to do remote calls
using the documented interfaces pmap_rmtcall() and callrpc()
calls to NFS will fail (actual times out) since UDP is no 
longer supported. 

The undocumented interface rpc_call() can be used to 
call into NFS since the protocol can specified, which 
also means the PMAPPROC_CALLIT protocol is not used.

It turns out privilege port are not needed to make
remote calls, at least with my testing. I'm thinking 
the only reason privilege ports were being uses was 
a side effect of create_rmtcall_fd() calling 
svc_tli_create() with an unbound socket. 

So the following patch simply binds the socket
before calling svc_tli_create() which means a
non-privilege port will be reserved for remote
calls. 

I'm thinking this is the simplest way to
not pollute the privilege port space. 

Steve Dickson (1):
  rmtcalls: Don't use privileged ports for remote calls.

 src/rpcb_svc_com.c | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

-- 
2.14.3

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux