Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Oct 2000 07:23:09 -0700
From:      Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
To:        vladimir@math.uic.edu
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: ipfw advice needed 
Message-ID:  <200010221423.e9MENTG10134@cwsys.cwsent.com>
In-Reply-To: Your message of "21 Oct 2000 18:22:40 -0000." <20001021182240.21355.qmail@math.uic.edu> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20001021182240.21355.qmail@math.uic.edu>, 
vladimir@math.uic.edu wri
tes:
> Dear -STABLE users, 
> 
> I am trying to setup ipfw rules to protect some
> of our crucial machines, including a file server.
> The system is 4.1.1-STABLE.    So far I've been
> using access lists on the router, but would like
> to get some extra security on the machine itself.
> One thing got me confused:  there is a couple of 
> daemons that are listening on the ports not
> listed in /etc/services.   For example, (lsof output):
> 
> ypserv      126   root    5u  IPv4 0xcefe2d80      0t0  TCP *:1023 (LISTEN)
> ypbind      128   root    5u  IPv4 0xcefe2b60      0t0  TCP *:1022 (LISTEN)
> mountd      135   root    4u  IPv4 0xcefe2940      0t0  TCP *:1021 (LISTEN)
> nfsd        137   root    3u  IPv4 0xcefe2720      0t0  TCP *:nfsd (LISTEN)
> rpc.lockd   161   root    4u  IPv4 0xce898900      0t0  UDP *:lockd
> rpc.lockd   161   root    5u  IPv4 0xcefe2500      0t0  TCP *:lockd (LISTEN)
> rpc.lockd   161   root    9u  IPv4 0xce89a6c0      0t0  UDP *:855
> rpc.statd   163   root    3u  IPv4 0xce898840      0t0  UDP *:990
> rpc.statd   163   root    4u  IPv4 0xcefe22e0      0t0  TCP *:1020 (LISTEN)
> 
> 
> ypbind listens on ports 1022, mountd on tcp port 1021, ypserv on tcp
> port 1023, statd on port 1020.    What do I do with those?
> Are these ports officially assigned or are they arbitrarily selected
> by these daemons when they start and register with the portmapper?
> Is there a range of TCP ports that I should keep opened for 
> incoming connections for these services to operate properly?
> Any hints would be appreciated.

These are RPC services.  You can use rpcinfo -p to get another view of 
this.  The port numbers are either arbitrarily defined by standard, e.g 
nfsd, and lockd, arbitrarily defined by an admin, e.g. Remedy, or 
randomly selected within a range, e.g. NIS, NIS+, mountd, rpc.statd, 
automountd, and amd.

Whether you want to keep certain ports open or closed depends on the 
application(s) you run and your security requirements.  Generally, RPC 
services should be blocked.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Team Leader, Sun/DEC Team   Internet:  Cy.Schubert@osg.gov.bc.ca
Open Systems Group, ITSD, ISTA
Province of BC





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010221423.e9MENTG10134>