Re: [Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config

On Thu, Oct 06, 2022 at 07:32:54AM -, msaxl wrote: > I think the biggest issue is the automatic upgrade from "classic" to > systemd.socket > It is very hard to consistently migrate every configuration. > I was hit by this issue because I had set > /proc/sys/net/ipv6/bindv6only=1, so ipv4 was

Re: [Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config

On Thu, Oct 06, 2022 at 02:34:40PM -, Corey Reichle wrote: > Nowhere was it documented that sshd now needs two configuration files, > just to tell it to listen on a port, and address it was already told to > do. False. It is documented in the manpage, in the default sshd_config file shipped

Re: [Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config

On Thu, Oct 06, 2022 at 02:34:40PM -, Corey Reichle wrote: > > Socket activation provides a smoother (runtime) UX for users > > SSHD configuration is not a user issue, but a systems administration > issue. Maybe, but more important is the UX for users of ssh clients who aren't trying to

Re: [Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config

On Thu, Oct 06, 2022 at 01:04:05PM -, Corey Reichle wrote: > If the point is to increase density, then sshd should just be off, and > not automatically started, unless it's required for work. Socket activation provides a smoother (runtime) UX for users, and is well established as a mechanism