Is this related to the SSH CVE that is blowing up the internet right now?
> After an 'apt upgrade' of openssh I am getting an unnerving error:
>
>> root@la:/home/kentborg# dpkg-reconfigure openssh-server
>> rescue-ssh.target is a disabled or a static unit not running, not
>> starting it.
>> ssh.so
On Tue, 2 Jul 2024 08:42:05 -0400
ma...@mohawksoft.com wrote:
> Is this related to the SSH CVE that is blowing up the internet right
> now?
Yes, inasmuch as "everyone" pushed out a fix for a recently discovered
regression bug. And yes, you should restart after updating to ensure
that the fixed ss
On 7/2/24 05:42, ma...@mohawksoft.com wrote:
Is this related to the SSH CVE that is blowing up the internet right now?
That is certainly why the update is out there. (Nasty bug!) But it looks
like there are no exploits in the wild, yet. One machine that would be
truly nasty if sshd quit runni
On Mon, 1 Jul 2024 13:53:17 -0700
Kent Borg wrote:
> After an 'apt upgrade' of openssh I am getting an unnerving error:
>
> > root@la:/home/kentborg# dpkg-reconfigure openssh-server
> > rescue-ssh.target is a disabled or a static unit not running, not
> > starting it.
> > ssh.socket is a disabl
On 7/2/24 13:24, Rich Pieri wrote:
TL;DR: these are notices, not errors.
socket units are, well, socket units. They're systemd's version of
(x)inetd.conf.
Yes, I looked at "ssh.socket" is and indeed it did look very inetd-like.
Which is what worried me! If sshd isn't going to start until some
