Re: Urgent news draft: The sshd service needs to be restarted after upgrading to openssh-9.8p1

2024-07-01 Thread Robin Candau
On 7/1/24 6:06 PM, David Runge wrote: On 2024-07-01 17:31:58 (+0200), Robin Candau wrote: # The sshd service needs to be restarted after upgrading to openssh-9.8p1 After upgrading to openssh-9.8p1, the existing SSH daemon will be unable to accept new connections. (See https://gitlab.archlinux

Re: Urgent news draft: The sshd service needs to be restarted after upgrading to openssh-9.8p1

2024-07-01 Thread David Runge
On 2024-07-01 17:31:58 (+0200), Robin Candau wrote: > > # The sshd service needs to be restarted after upgrading to openssh-9.8p1 > > After upgrading to openssh-9.8p1, the existing SSH daemon will be unable to > accept new connections. (See > https://gitlab.archlinux.org/archlinux/packaging/pack

Urgent news draft: The sshd service needs to be restarted after upgrading to openssh-9.8p1

2024-07-01 Thread Robin Candau
Hi everyone, As you might have heard by now (or experienced it already), the latest openssh-9.8p1 release requires the sshd daemon to be restarted otherwise new connections cannot establish (the one used to upgrade the package remains intact though). To prevent people from eventually blocking