Once upon a time, Richard W.M. Jones rjones@redhat.com said:
The DoS attack is described here:
https://bugs.archlinux.org/task/62248
... and it sounds like a bug in systemd. Surely this same attack applies to any socket-activated service so should be fixed in systemd? I don't recall inetd having the same problem.
(x)inetd would shut a port under heavy net-connection load for a short period, but systemd seems to shut it permanently under those conditions. For systemd to replace inetd-type socket activation, it needs to have a timeout on the disable.
This probably isn't a high priority though, because very few things support inetd-type modes anymore.