5 ms·

Hey, someone rediscovered xinetd

klodolph 4y ago
I remember using xinetd, and while xinetd does do the job… sometimes… systemd is much more comprehensive, so you don’t need to fuss about with different configs for xinetd, cron, init.d, etc. This is especially nice since the number of config options has skyrocketed, so systemd really simplifies administration (in my experience, at least).
oblio 4y ago
> Hey, someone rediscovered xinetd 1. http://0pointer.de/blog/projects/systemd.html http://0pointer.de/blog/projects/systemd.html Replacing inetd was a systemd design goal. 2. Snark for someone learning is a bad move.
- xdfgh1112 4y ago
  It was in jest, xinetd is clearly not as powerful as systemd and I'm glad to be rid of it.
athrun 4y ago
It's challenging to restart a service without dropping connections with xinetd. Even more so when the process is misbehaving, has children, and is not exiting cleanly.
KingOfCoders 4y ago
Isn't it astonishing? I've been using Linux pre-Slackware with downloading boot.tgz and root.tgz on two floppy drives, wrestled with M4 and sendmail, have been writing internet applications for 35+ years but never used a Linux daemon to manage my applications. You're never too old to learn I guess.
- xdfgh1112 4y ago
  I use systemd at work and I have finally learned to love it. Still don't like binary logs but the timers, watchdog and sandboxing features are wonderful.
  - panzi 4y ago
    I configurated the systemd services at work to redirect the services' output to syslog.
blueflow 4y ago
I once won a backdoor contest by installing a systemd socket who launched /bin/sh as root. At this point, people don't question why systemd is being bound to some random ports.
- biorach 4y ago
  were you able to install this without using sudo?
  - blueflow 4y ago
    In the contest you had root access for a limited amount of time, but you can also do it via a user unit.
    - Xylakant 4y ago
      But then you should only get the users account as shell, so while this is a neat trick, being able to gain persistent root if you are already root is not that hard.
      - blueflow 4y ago
        It was part of the contest that your enemy team is not able to detect and remove your backdoor. The obscurity of systemd sockets was my winning move.
        wmrtynhber 4y ago
        systemd doesn't bind to random ports without being told to. if the blue team didn't stop and say "why is anything listening on port %d", they're a trash blue team.
        xorcist 4y ago
        Clearly you have not used systemd and friends much. It is an ecosystem of daemons that does a lot of things, some of which are guaranteed to surprise you. The specifics of which will vary between releases. I could easily see some random systemd utility binding a non standard port without anyone taking notice.
vegai_ 4y ago
>Hey, someone rediscovered xinetd With a much better piece of software, exactly.

I remember using xinetd, and while xinetd does do the job… sometimes… systemd is much more comprehensive, so you don’t need to fuss about with different configs for xinetd, cron, init.d, etc. This is especially nice since the number of config options has skyrocketed, so systemd really simplifies administration (in my experience, at least).

oblio 4y ago

> Hey, someone rediscovered xinetd 1. http://0pointer.de/blog/projects/systemd.html http://0pointer.de/blog/projects/systemd.html Replacing inetd was a systemd design goal. 2. Snark for someone learning is a bad move.

xdfgh1112 4y ago
It was in jest, xinetd is clearly not as powerful as systemd and I'm glad to be rid of it.

athrun 4y ago

It's challenging to restart a service without dropping connections with xinetd. Even more so when the process is misbehaving, has children, and is not exiting cleanly.

KingOfCoders 4y ago

Isn't it astonishing? I've been using Linux pre-Slackware with downloading boot.tgz and root.tgz on two floppy drives, wrestled with M4 and sendmail, have been writing internet applications for 35+ years but never used a Linux daemon to manage my applications. You're never too old to learn I guess.

xdfgh1112 4y ago
I use systemd at work and I have finally learned to love it. Still don't like binary logs but the timers, watchdog and sandboxing features are wonderful.
- panzi 4y ago
  I configurated the systemd services at work to redirect the services' output to syslog.

blueflow 4y ago

I once won a backdoor contest by installing a systemd socket who launched /bin/sh as root. At this point, people don't question why systemd is being bound to some random ports.

biorach 4y ago
were you able to install this without using sudo?
- blueflow 4y ago
  In the contest you had root access for a limited amount of time, but you can also do it via a user unit.
  - Xylakant 4y ago
    But then you should only get the users account as shell, so while this is a neat trick, being able to gain persistent root if you are already root is not that hard.
    - blueflow 4y ago
      It was part of the contest that your enemy team is not able to detect and remove your backdoor. The obscurity of systemd sockets was my winning move.
      - wmrtynhber 4y ago
        systemd doesn't bind to random ports without being told to. if the blue team didn't stop and say "why is anything listening on port %d", they're a trash blue team.
        xorcist 4y ago
        Clearly you have not used systemd and friends much. It is an ecosystem of daemons that does a lot of things, some of which are guaranteed to surprise you. The specifics of which will vary between releases. I could easily see some random systemd utility binding a non standard port without anyone taking notice.

vegai_ 4y ago

>Hey, someone rediscovered xinetd With a much better piece of software, exactly.