Re: nfsd support for tcp_wrapper -> General RPC solution
From: Borja Marcos (borjamar@sarenet.es)
Date: 02/09/01
- Next message: dannyman: "Re: How builds OpenSSH 2.3?"
- Previous message: Kris Kennaway: "Re: How builds OpenSSH 2.3?"
- In reply to: Alfred Perlstein: "Re: nfsd support for tcp_wrapper -> General RPC solution"
- Next in thread: Alfred Perlstein: "Re: nfsd support for tcp_wrapper -> General RPC solution"
- Reply: Alfred Perlstein: "Re: nfsd support for tcp_wrapper -> General RPC solution"
- Reply: Dan Debertin: "Re: nfsd support for tcp_wrapper -> General RPC solution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 09 Feb 2001 23:52:22 +0100 From: Borja Marcos <borjamar@sarenet.es> To: freebsd-security@freebsd.org
Alfred Perlstein wrote:
> This is a really flawed idea.
Humm. Yours is a flawed reading of my message? ;-)
> All portmap does is provide a name/version/protocol mapping of a
> service to a tcp/udp port. One can trivially do a portscan of
> a box running RPC services and figure out which are open. You
> don't need portmap to brute force finding out where a remote
> vulnerable service is located.
But if portmap can set up the right rules for ipfw,
the brute force portscan will have no success. (read below)
>
> In fact because afaik NFS always uses a well known port, you really
> don't need portmap to map it, you just need to use the port,
> portmapper for NFS is just a formality.
>
> Ok, with that out of the window, we _could_ consider mucking userland
> mountd to use tcpwrappers to graft an ACL to what's in /etc/exports.
> This is also a bad idea, one can just brute force the NFS
> cookie/filehandle required to gain access, then contact the NFS
> port.
>
> The solution is to use a firewall.
Yes, and what about having portmap set the right firewall
rules to protect RPC services? Whenever a service registers itself
to portmap, it puts firewall rules to block access to the port.
That is what I am proposing!
Yes, NFS uses a fixed port, but not other RPC services.
Borja.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- Next message: dannyman: "Re: How builds OpenSSH 2.3?"
- Previous message: Kris Kennaway: "Re: How builds OpenSSH 2.3?"
- In reply to: Alfred Perlstein: "Re: nfsd support for tcp_wrapper -> General RPC solution"
- Next in thread: Alfred Perlstein: "Re: nfsd support for tcp_wrapper -> General RPC solution"
- Reply: Alfred Perlstein: "Re: nfsd support for tcp_wrapper -> General RPC solution"
- Reply: Dan Debertin: "Re: nfsd support for tcp_wrapper -> General RPC solution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|