Hacker News Reader

Hacker News

Comment by xdfgh1112 | Hacker News Reader

Parent Full thread

xdfgh1112

Hey, someone rediscovered xinetd

View on HN

> Hey, someone rediscovered xinetd

1. http://0pointer.de/blog/projects/systemd.html

Replacing inetd was a systemd design goal.

2. Snark for someone learning is a bad move.

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

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.

were you able to install this without using sudo?

In the contest you had root access for a limited amount of time, but you can also do it via a user unit.

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.

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.

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.

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.

That would be the distro's problem, not systemd. Any of those utilities are going to be optional, the distro has to consciously enable them and ship them in a package for it to make it to you at all. A lot of commenters seem to misunderstand that systemd is not forcing distros to do anything. All they really do is provide a set of tools for distro maintainers to choose from.

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).

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.

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.

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.

I configurated the systemd services at work to redirect the services' output to syslog.

>Hey, someone rediscovered xinetd

With a much better piece of software, exactly.

Reply on news.ycombinator.com