> telnet on the other hand is usually run by inetd (or xinetd etc). This
> means inetd listens on port 23 and when a connection is attempted it
> accepts and starts the telnet daemon. In this case you must configure
> inetd not to listen on that port (/etc/services) and/or not to connect a
> daemon to it (/etc/inetd.conf). I would guess the former is strictly
> cleverer as inetd is not exposed either.
More misinformation...
It is a common misconception that removing lines from /etc/services
disables stuff.
inetd does not listen on ports according to the /etc/services file.
It listens on the ports that have entries in /etc/inetd.conf.
/etc/services is merely a name-to-number mapping file for ports.
So that when you do (for example):
$ telnet somehost smtp
it can convert "smtp" to 25. Also when you do:
$ netstat
it can convert 25 to "smtp".
And /etc/services can be centralised via NIS (and probably also
via LDAP).
Later,
Kenn
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
