On Wed, Feb 19, 2020 at 3:00 PM Mike Gilbert wrote:
> On Wed, Feb 19, 2020 at 3:41 PM Michael Jones wrote:
> >
> > How does this effect systemd's socket activation?
> >
> > E.g. The systemd sshd.socket unit file.
>
> Please avoid top-posting.
>
> When socket-activated, a separate instance of
On Wed, Feb 19, 2020 at 12:02:51PM -0800, Patrick McLean wrote:
> Title: OpenSSH 8.2_p1 running sshd breakage
> Author: Patrick McLean
> Posted: 2020-02-21
> Revision: 1
> News-Item-Format: 2.0
> Display-If-Installed:
> If sshd is running, and a system is upgraded from to
On Wed, Feb 19, 2020 at 3:41 PM Michael Jones wrote:
>
> How does this effect systemd's socket activation?
>
> E.g. The systemd sshd.socket unit file.
Please avoid top-posting.
When socket-activated, a separate instance of sshd is spawned for each
connection. I don't think any action is needed
How does this effect systemd's socket activation?
E.g. The systemd sshd.socket unit file.
On Wed, Feb 19, 2020 at 2:12 PM Mike Gilbert wrote:
> On Wed, Feb 19, 2020 at 3:02 PM Patrick McLean
> wrote:
> >
> > Title: OpenSSH 8.2_p1 running sshd breakage
> > Author: Patrick McLean
> > Posted:
On Wed, Feb 19, 2020 at 3:02 PM Patrick McLean wrote:
>
> Title: OpenSSH 8.2_p1 running sshd breakage
> Author: Patrick McLean
> Posted: 2020-02-21
> Revision: 1
> News-Item-Format: 2.0
> Display-If-Installed:
> If sshd is running, and a system is upgraded from to >=net-misc/openssh-8.2_p1,
Title: OpenSSH 8.2_p1 running sshd breakage
Author: Patrick McLean
Posted: 2020-02-21
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: =net-misc/openssh-8.2_p1, any new ssh connection will fail until sshd is
restarted.
Before restarting sshd, it is *strongly* recommended that you test
