On Wed, 2009-07-15 at 17:42 -0400, Chuck Lever wrote:
> TI-RPC rpcbind operations provide not just a port number, but a full
> socket address the client should connect to. This allows rpcbind to
> redirect RPC traffic to specific network interfaces or servers. The
> Linux kernel rpcbind client implementation currently ignores the
> address.
>
> Expand the ->set_port transport method so an address is passed to
> transports during an RPC bind operation. Additional changes to
> individual client transports will be required to replace the peer
> address after an rpcbind operation.
Now I'm worried. We've just spent a lot of time implementing RPCSEC_GSS
security, and yet we're going allow an AUTH_SYS-based RPC call to tell
us to change an IP address that the user supplied us with? It was bad
enough when we allowed it to set the port number...
Trond
--
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
