No inetd conf on linux

Telnet Server not starting

I am installing Ubuntu Server 13.10 and cant get telnet working on the server. I have installed both xinet.d & telnetd thru apt-get and restarted xinetd but nothing is started when I do a netstat -l . In googling, the trouble I see mention of adding telnet stream tcp wait telnetd /usr/sbin/tcpd /usr/sbin/in.telnetd line to /etc/inetd.conf . I have no inetd.conf . I see that inetd has been depracated and I put the line in xinetd.conf and restarted xinetd service but still no telnet listening. Can someone advise me on what the proper settings for the telnet server and what files they should be in. Here is the content of my xinetd.conf file:

# Simple configuration file for xinetd # # Some defaults, and include /etc/xinetd.d/ defaults < # Please note that you need a log_type line to be able to use log_on_success # and log_on_failure. The default is the following : # log_type = SYSLOG daemon info >includedir /etc/xinetd.d #:STANDARD: These are standard services. telnet stream tcp nowait telnetd /usr/sbin/tcpd /usr/sbin/in.telnetd 

Why are you using telnet? It is an obsolete and insecure protocol. Use ssh instead: it’s secure, faster ( uses compression ) and has other nifty features, like the ability to forward ports.

You seem to think that /etc/inetd.conf and xinetd.conf use the same format. Have you read man xinetd , man -k xinetd , man inetd , man -k inetd , man telnetd ? Does /etc/default/telnetd exist? Have you done grep telnet /var/log/* ?

Источник

Thread: Where has inetd.conf gone?

Just Give Me the Beans!

Where has inetd.conf gone?

Whatever happened to good old inetd.conf or xinetd.conf? Back in the day, lines in these files were handy ways of insuring that apps like smb and telnetd would (or would not) be automatically started at boot. Since neither of these configuration files exists in /etc anymore, I can only assume their function has been taken over by some other script or process to be run at startup. With earlier versions of Ubuntu, one could even turn Samba startup on or off using the «startup applications» applet under the system->preference menu, but this, too, has disappeared. So where has this control gone? What determines whether such applications get started? The «Ubuntu Documentation», as is often the case, is less than helpful at providing any enlightenment regarding the actual workings of the system or documenting arbitrary changes made to it from version to version.

So my questions are — (1)what has now taken over the function of inetd.conf or xinetd.conf; (2)how can networks services such as telnetd be added or removed from the startup and (3)if one these files is created and put into /etc will its contents still be read and executed?

Ubuntu addict and loving it

Join Date Nov 2008 Location Boston MetroWest Beans 16,074 —> Beans 16,074 Distro Kubuntu 22.04 Jammy Jellyfish

Re: Where has inetd.conf gone?

Many services that used to have a single consolidated configuration file now use separate files for each service. This enables package installers to place the file for a specific service in the configuration directory. In the case of xinetd, the configuration files are stored in /etc/xinetd.d/.

«sudo apt-get install xinetd» will install the binary and create the /etc/xinetd.d/ directory. You’ll also get an /etc/xinetd.conf file that essentially tells xinetd to traverse the xinetd.d directory.

The original inetd has been largely deprecated in favor of the more powerful xinetd.

More and more server daemons are designed to run securely as standalone programs rather than being invoked by xinetd. I still use it to run a few specific services for which I need to control access via hosts.allow and hosts.deny. But the major servers — SSH, Apache, MySQL/PostgreSQL, sendmail/Postfix, etc. — all run as standalone daemons these days.

Источник

UNIX for Dummies Questions & Answers

27, 0

I’m trying to set up swat on my linux box at home and when i read the man pages on it it says that i have to edit a file called inetd.conf but i did a search like
find / -name inetd.conf
but it only comes up with this.
/etc/linuxconf/archive/Home-Office/etc/inetd.conf
find: /mnt/cdrom: Input/output error
find: /mnt/floppy: Input/output error
find: /proc/975/fd: No such file or directory

so i moved to the only one it found but it say that the file is empty
how do i go about getting this file agian.
or would i be able to recreat it by just vi ing a new file in /etc
and calling it inetd.conf

Neo

19,118, 3,359

# See "man 8 inetd" for more information. # # If you make changes to this file, either reboot your machine or send the # inetd a HUP signal: # Do a "ps x" as root and look up the pid of inetd. Then do a # "kill -HUP ". # The inetd will re-read this file whenever it gets that signal. # #       # # The first 4 services are really only used for debugging purposes, so # we comment them out since they can otherwise be used for some nasty # denial-of-service attacks. If you need them, uncomment them. # echo stream tcp nowait root internal # echo dgram udp wait root internal # discard stream tcp nowait root internal # discard dgram udp wait root internal # daytime stream tcp nowait root internal # daytime dgram udp wait root internal # chargen stream tcp nowait root internal # chargen dgram udp wait root internal #time stream tcp nowait root internal #time dgram udp wait root internal # # These are standard services. # #ftp stream tcp nowait root /usr/sbin/tcpd wu.ftpd -l -i -a #telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd # # Use this one instead if you want to snoop on telnet users (try to use this # for ethical purposes, ok folks?), and see 'man ttysnoop' and /etc/snooptab # for further instructions: # telnet stream tcp nowait root /usr/sbin/tcpd in.telnetsnoopd # # This is for BSD sendmail. NOTE: It's not a good idea to uncomment this # one, since sendmail is already set up to run as a daemon in /etc/rc.d/rc.M. # But, if you really want to run sendmail this way for some reason, you'll # need to uncomment the smtp line below AND change the line in /etc/rc.d/rc.M # to run sendmail like this: /usr/sbin/sendmail -q30m # . otherwise the queue will not be processed. # smtp stream tcp nowait root /usr/sbin/tcpd sendmail -bs # # The comsat daemon notifies the user of new mail when biff is set to y: #comsat dgram udp wait root /usr/sbin/tcpd in.comsat # # Shell, login, exec and talk are BSD protocols. # #shell stream tcp nowait root /usr/sbin/tcpd in.rshd -L #login stream tcp nowait root /usr/sbin/tcpd in.rlogind # exec stream tcp nowait root /usr/sbin/tcpd in.rexecd # talk dgram udp wait root /usr/sbin/tcpd in.talkd #ntalk dgram udp wait root /usr/sbin/tcpd in.talkd # # Kerberos authenticated services # ktelnet stream tcp nowait root /usr/local/sbin/telnetd telnetd -a user # klogin stream tcp nowait root /usr/sbin/tcpd rlogind -k # eklogin stream tcp nowait root /usr/sbin/tcpd rlogind -k -x # kshell stream tcp nowait root /usr/sbin/tcpd rshd -k # # Services run ONLY on the Kerberos server # # krbupdate stream tcp nowait root /usr/sbin/tcpd registerd # kpasswd stream tcp nowait root /usr/sbin/tcpd kpasswdd # # Pop et al # # pop2 stream tcp nowait root /usr/sbin/tcpd in.pop2d # Traditional BSD-based in.pop3d: #pop3 stream tcp nowait root /usr/sbin/tcpd in.pop3d # GNU pop3d: pop3 stream tcp nowait root /usr/sbin/tcpd gnu-pop3d # The ipop3d POP3 server is part of the Pine distribution. If you've # installed the Pine package, you may wish to switch to ipop3d by # commenting out the pop3 line above, and uncommenting the pop3 line below. # pop3 stream tcp nowait root /usr/sbin/tcpd ipop3d imap2 stream tcp nowait root /usr/sbin/tcpd imapd # # The Internet UUCP service. # # uucp stream tcp nowait uucp /usr/sbin/tcpd /usr/lib/uucp/uucico -l # # Tftp service is provided primarily for booting. Most sites # run this only on machines acting as "boot servers." # # tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd # bootps dgram udp wait root /usr/sbin/in.bootpd in.bootpd # # Finger, systat and netstat give out user information which may be # valuable to potential "system crackers." Many sites choose to disable # some or all of these services to improve security. # Try "telnet localhost systat" and "telnet localhost netstat" to see that # information yourself! # #finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd -u # systat stream tcp nowait nobody /usr/sbin/tcpd /bin/ps -auwwx # netstat stream tcp nowait root /usr/sbin/tcpd /bin/netstat -a # # Ident service is used for net authentication # Since we start identd as nobody, it can't write a .pid file in /var/run, so tell it # to use /dev/null. This is of little importance unless you run identd as a # standalone daemon anyway. auth stream tcp wait nobody /usr/sbin/in.identd in.identd -P/dev/null # # These are to start Samba, an smb server that can export filesystems to # Pathworks, Lanmanager for DOS, Windows for Workgroups, Windows95, Lanmanager # for Windows, Lanmanager for OS/2, Windows NT, etc. # If you're running smbd and nmbd from daemons in /etc/rc.d/rc.samba, then you # shouldn't uncomment these lines. # netbios-ssn stream tcp nowait root /usr/sbin/smbd smbd # netbios-ns dgram udp wait root /usr/sbin/nmbd nmbd # # Sun-RPC based services. #  # # rstatd/1-3 dgram rpc/udp wait root /usr/sbin/tcpd rpc.rstatd # rusersd/2-3 dgram rpc/udp wait root /usr/sbin/tcpd rpc.rusersd # walld/1 dgram rpc/udp wait root /usr/sbin/tcpd rpc.rwalld # # End of inetd.conf.

Источник

SomoIT.net

IT System Administration – Sysadmin tips, tricks and tutorials

Linux – cannot found / missing inetd.conf

Trying to configure a new inetd service needed for my Icinga (see Linux – Create custom inetd service), but i have not been able to find the inetd.conf file.
It seems inetd is not installed by default in the last Debian versions (mine is 9 – stretch). Luckily, it is packetized in the inetutils-inetd

# apt-get install inetutils-inetd 

ls -l /etc/inetd.conf -rw-r--r-- 1 root root 1128 Nov 24 09:25 /etc/inetd.conf 

root@debian:~# /etc/init.d/inetutils-inetd restart [ ok ] Restarting inetutils-inetd (via systemctl): inetutils-inetd.service. 

Update: Tried to configure a service that runs a bash script but no way to make it work

root@debian:~# tail -1 /etc/inetd.conf remote-commands stream tcp nowait root /root/SCRIPTS/remote-commands.sh root@debian:~# cat /etc/services | grep remote-commands remote-commands 3335/tcp # Remote commands root@debian:~# ls -l /root/SCRIPTS/remote-commands.sh -rwxr-xr-x 1 root root 162 Dec 7 09:44 /root/SCRIPTS/remote-commands.sh 

 root@debian:~# /etc/init.d/inetutils-inetd status ● inetutils-inetd.service - LSB: inetd sysv init script Loaded: loaded (/etc/init.d/inetutils-inetd; generated; vendor preset: enabled) Active: active (running) since Thu 2017-12-07 09:39:13 CET; 6min ago Docs: man:systemd-sysv-generator(8) Process: 8869 ExecStop=/etc/init.d/inetutils-inetd stop (code=exited, status=0/SUCCESS) Process: 8874 ExecStart=/etc/init.d/inetutils-inetd start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 4915) CGroup: /system.slice/inetutils-inetd.service └─8882 /usr/sbin/inetutils-inetd Dec 07 09:39:13 debian systemd[1]: Stopped LSB: inetd sysv init script. Dec 07 09:39:13 debian systemd[1]: Starting LSB: inetd sysv init script. Dec 07 09:39:13 debian inetutils-inetd[8874]: Starting internet superserver: inetd. Dec 07 09:39:13 debian systemd[1]: Started LSB: inetd sysv init script. Dec 07 09:45:49 debian inetd[12955]: cannot execute /root/SCRIPTS/remote-commands.sh: Bad address 

I have not yet been able to solve the problem…
Anyway I have found another simple way to configure a simple tcp daemon listening. Wait for my post 😉

Источник