Re: Dropping of sshd.socket unit

2023-09-11 Thread Lennart Poettering
On Mo, 21.08.23 11:07, Lennart Poettering (mzerq...@0pointer.de) wrote: > On Do, 17.08.23 08:25, Chris Adams (li...@cmadams.net) wrote: > > > Once upon a time, Lennart Poettering said: > > > Yes, and if this is not what you want, then disable the > > > ratelimit. That's what I am saying? > > > >

Re: Dropping of sshd.socket unit

2023-08-21 Thread Leslie Satenstein via devel
Sounds good!  Leslie Satenstein On Monday, August 21, 2023 at 05:08:06 a.m. GMT-4, Lennart Poettering wrote: On Do, 17.08.23 08:25, Chris Adams (li...@cmadams.net) wrote: > Once upon a time, Lennart Poettering said: > > Yes, and if this is not what you want, then disable the >

Re: Dropping of sshd.socket unit

2023-08-21 Thread Lennart Poettering
On Do, 17.08.23 08:25, Chris Adams (li...@cmadams.net) wrote: > Once upon a time, Lennart Poettering said: > > Yes, and if this is not what you want, then disable the > > ratelimit. That's what I am saying? > > It would be useful for systemd to have "cooldown periods" for things, > similar to ine

Re: Dropping of sshd.socket unit

2023-08-17 Thread Leon Fauster via devel
Am 17.08.23 um 20:14 schrieb Tomasz Torcz: On Thu, Aug 17, 2023 at 08:25:10AM -0500, Chris Adams wrote: Once upon a time, Lennart Poettering said: Yes, and if this is not what you want, then disable the ratelimit. That's what I am saying? It would be useful for systemd to have "cooldown peri

Re: Dropping of sshd.socket unit

2023-08-17 Thread Tomasz Torcz
On Thu, Aug 17, 2023 at 08:25:10AM -0500, Chris Adams wrote: > Once upon a time, Lennart Poettering said: > > Yes, and if this is not what you want, then disable the > > ratelimit. That's what I am saying? > > It would be useful for systemd to have "cooldown periods" for things, > similar to inet

Re: Dropping of sshd.socket unit

2023-08-17 Thread Chris Adams
Once upon a time, Lennart Poettering said: > Yes, and if this is not what you want, then disable the > ratelimit. That's what I am saying? It would be useful for systemd to have "cooldown periods" for things, similar to inetd and classic init, where misbehaving things (whether services or sockets

Re: Dropping of sshd.socket unit

2023-08-17 Thread Lennart Poettering
On Di, 15.08.23 18:17, Dmitry Belyavskiy (dbely...@redhat.com) wrote: > Dear Lennart, > > I'm sorry, I don't get. > > Quoting the > https://www.freedesktop.org/software/systemd/man/systemd.socket.html#TriggerLimitIntervalSec= > > Configures a limit on how often this socket unit may be activated >

Re: Dropping of sshd.socket unit

2023-08-15 Thread Dmitry Belyavskiy
Dear Lennart, I'm sorry, I don't get. Quoting the https://www.freedesktop.org/software/systemd/man/systemd.socket.html#TriggerLimitIntervalSec= Configures a limit on how often this socket unit may be activated within a specific time interval. The TriggerLimitIntervalSec= may be used to configur

Re: Dropping of sshd.socket unit

2023-08-07 Thread Petr Menšík
Wouldn't a relative simple change to fix this would be explicit TriggerLimitBurst=0 until some form of timed reactivation is implemented? Especially for sshd.socket that change would seem safer. It is not a big deal for sshd, it seems to be quite small anyway. Could simple [Unit] Restart=on-f

Re: Dropping of sshd.socket unit

2023-08-07 Thread Lennart Poettering
On Do, 03.08.23 11:29, Dmitry Belyavskiy (dbely...@redhat.com) wrote: > Dear colleagues, > > I've pushed a fresh build of OpenSSH to rawhide. > We decided to drop the sshd.socket unit from rawhide. We don't think > it's worth going through the changes process, but would like to > provide a heads-u

Re: Dropping of sshd.socket unit

2023-08-04 Thread Chris Adams
Once upon a time, Steve Grubb said: > Yes, as one of the authors of xinetd, I pointed this out long ago. But they > said they were not trying to replace xinetd and if people want a more full > featured experience, use xinetd. Except... wasn't there a big push to replace xinetd with systemd sock

Re: Dropping of sshd.socket unit

2023-08-04 Thread Steve Grubb
On Friday, August 4, 2023 8:42:18 AM EDT Chris Adams wrote: > Once upon a time, Richard W.M. Jones 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-acti

Re: Dropping of sshd.socket unit

2023-08-04 Thread Chris Adams
Once upon a time, Richard W.M. Jones 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 th

Re: Dropping of sshd.socket unit

2023-08-04 Thread Richard W.M. Jones
On Thu, Aug 03, 2023 at 11:29:03AM +0200, Dmitry Belyavskiy wrote: > Dear colleagues, > > I've pushed a fresh build of OpenSSH to rawhide. > We decided to drop the sshd.socket unit from rawhide. We don't think > it's worth going through the changes process, but would like to > provide a heads-up.

Re: Dropping of sshd.socket unit

2023-08-03 Thread Qiyu Yan
Just a question, do we have any mechanism to migrate users from sshd.socket to sshd.service? Otherwise someone may suddenly lose access to their headless systems after an upgrade. 在 2023/8/3 10:29, Dmitry Belyavskiy 写道: Dear colleagues, I've pushed a fresh build of OpenSSH to rawhide. We deci

Dropping of sshd.socket unit

2023-08-03 Thread Dmitry Belyavskiy
Dear colleagues, I've pushed a fresh build of OpenSSH to rawhide. We decided to drop the sshd.socket unit from rawhide. We don't think it's worth going through the changes process, but would like to provide a heads-up. See the details in https://bugzilla.redhat.com/show_bug.cgi?id=2025716. -- D