Re: Dropping of sshd.socket unit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Once upon a time, Richard W.M. Jones <rjones@xxxxxxxxxx> 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.
-- 
Chris Adams <linux@xxxxxxxxxxx>
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux