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

Re: daemons -- who needs'em?



On Thu, Apr 27, 2000 at 06:50:49AM -0500, w trillich wrote:
> to paraphrase bob hope's theme--thanks for the summaries!
> 
> 
> > >  2206 ?        S      0:00 /sbin/portmap
> > Portmapper for the RPC-based services (kinda a dispatch for them)
> > > portmap = something to do with Remote-Procedure-Call?
> > precisely
> 
> can i ditch it? is it essential somehow?

only if you need to use NFS (No File Security) or rwho, ruptime et al
(ie useless crap)

> as in, for firewall/ipmasq router? (if so, yes!)

have you configured it? if not then you probably don't need it, as it
does not thing very useful until you tell it to.  

rinetd would be useful if for example you wnated to run an ftp server
inside your firewall, but have people connect to the firewall for ftp
service.  it would make it look like there was ftp running on the
firewall but would just redirect any connections to wherever you told
it to (the internal host).  if your just using IP NAT to give a bunch
of machines net access but are not running any services on the
internal machines that need to be accessable to the outside you don't
need rinetd.

> 
> how about ypbind? what's that, and why?

its for NIS (Network INsecurity ;-) [1]) you would need it if you wanted
to say have all your machines authenticate against one, instead of
having a different username password on each machine.  (thats just one
thing NIS can do) problem with NIS is its not all that secure, NIS+
solves much of the security issues but AFAIK there is no
implementation for GNU/Linux.

[1] the real name is Network Information service iirc.  used to be
called Yellow Pages but then whoever makes phone books sued over it.
(or something like that)

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgprZiF0EEgIE.pgp
Description: PGP signature


Reply to: