On 7/1/17 23:12, Vladimir Sedach wrote:
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDc+4x1XblOzyfHAzOCbM00FB/VglYg0PvOSL8FuQKQ/ vas@t43.lan
Added the key to file://comon-lisp.net/home/vsedach/.ssh/authorized_keys, and hopefully didn't munge the permissions too badly.
Let us know if you need more help re-establishing control.
In general, I find our SSH situation a bit wonky, presumably as we are still running an older Debian distribution that doesn't have all the latest SSH conventions well established. Erik has been working on moving us over to the latest Debian ("Stretch") which I would argue would be the sane point to try to figure out why sshd on that host behaves the way it does.