On 7/1/24 05:36, Genes Lists wrote:
The new openssh works just fine and this is just a little note to those
of us with remote machines.
After updating both client and remote machine(s) its important to
restart sshd.
If you don't restart sshd, and then attempt to ssh into the remote, it
may fai
On Mon, 1 Jul 2024 20:57:31 +0200
mpan wrote:
> > (…) If you don't restart sshd, and then attempt to ssh into the remote,
> > it may fail with: (…)
>Note that one *must* restart sshd regardless. Updating the files
> isn’t fixing the vulnerability. The old, vulnerable version of the
> proc
(…) If you don't restart sshd, and then attempt to ssh into the remote,
it may fail with: (…)
Note that one *must* restart sshd regardless. Updating the files
isn’t fixing the vulnerability. The old, vulnerable version of the
process is still running until the service is restarted.
Cheers
On Mon, Jul 01, 2024 at 12:59:05 +0200, Geert Hendrickx wrote:
> More specifically, the upgraded server logs the following:
> sshd: -R not supported here
>
> (when forked by a not-restarted master process)
>
> I can't immediatly spot in the ChangeLog what is causing this, but it
> certainly warra
On Mon, Jul 01, 2024 at 06:36:50 -0400, Genes Lists wrote:
> After updating both client and remote machine(s) its important to
> restart sshd.
>
> If you don't restart sshd, and then attempt to ssh into the remote,
> it may fail with:
>
>kex_exchange_identification: read: Connection reset by
The new openssh works just fine and this is just a little note to those
of us with remote machines.
After updating both client and remote machine(s) its important to
restart sshd.
If you don't restart sshd, and then attempt to ssh into the remote, it
may fail with:
kex_exchange_identificatio
