SSH public key auth broken after upgrade to TrueNAS 13

Darren David

Explorer
Joined
Feb 27, 2014
Messages
54
Hi all-

I recently upgraded to TrueNAS 13.0 and something about the upgrade broke SSH keypair auth. I use SecureCRT on Windows, and both PCs that I was able to SSH in from using my keypair for auth stopped working after the upgrade. Password login works fine.

Has something changed with FreeBSD 13 (or TrueNAS) that I need to adjust for?

Darren
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Although this is in the context of replication, I think it's going to be relevant for you as well:
1661301388736.png

Source:
 
  • Like
Reactions: Maq

marahin

Cadet
Joined
Jul 10, 2022
Messages
5
Hi,

one of my users have been using SSHFS to connect to my TrueNAS Core instance. After upgrading to TrueNAS 13 the SSHFS connection broke. User in question has CentOS 6.
Code:
$ ssh xxxxx@yyyyy
no hostkey alg

and the SSHFS connection:
Code:
# sshfs -o allow_other -o nonempty,reconnect,ServerAliveInterval=30,ServerAliveCountMax=2880 -o cache=no xxxx@yyyyyy:/mnt/somethingsomething /mnt/somethingsomething
read: Connection reset by peer

Adding
Code:
PubkeyAcceptedAlgorithms +ssh-rsa
did not help on its own, I also had to add
Code:
HostKeyAlgorithms +ssh-rsa
as suggested here: https://unix.stackexchange.com/questions/679451/sshd-no-hostkey-alg-fixed-but-still-confused

1669114230262.png
 

FrankWard

Explorer
Joined
Feb 13, 2023
Messages
71

FrankWard

Explorer
Joined
Feb 13, 2023
Messages
71
I was able to get it working by adding the public key directly to the user account. I'm able to remote into SSH using SecureCRT, WinSCP, and FileZilla. Still can't get it to work with VSCode.
 
Top