Theo <
theom+news@chiark.greenend.org.uk> wrote:
A. Dumas <alexandre@dumas.fr.invalid> wrote:
Grant Taylor <gtaylor@tnetconsulting.net> wrote:
On 7/14/22 10:44 PM, A. Dumas wrote:
SHA1 support can be re-enabled in /etc/ssh/ssh_config with
"PubkeyAcceptedKeyTypes +ssh-rsa" and a reboot but it is indeed unsafe. >>>
You shouldn't need to reboot. You should be able to restart the SSH
daemon independently, without a reboot.
Well, of course, but if a user can't even google their problem and a
possible solution, then restarting a service might also be too much to ask. >> Reboot is much easier and also works ¯\_(ツ)_/¯
Maybe, although:
sudo service ssh reload
(or 'sudo service ssh restart')
isn't hard. It's more complicated to edit the config file.
You see, I would say force-reload, just to be sure (reloads if possible, otherwise restarts). But also, I am not sure if any other services depend
on that config change. Probably not, but again, just to be sure... Is every service completely self-contained under systemd? I'm not an admin so I
don't know. If I were behind the keyboard I would try to reload and test if
it works. Ah well.
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)