SOLVED Getting shell SSH to use key

[badincite]

Trying to setup SSH to use this key to get into my esxi server. I've added the public key in the authorized_keys of esxi I cant seem to get the shell console to use the key. Anything else I need to do its still asking for the password everytime?

Current Setup

 

[danb35]

've added the public key in the authorized_keys of esxi

Which public key have you added? What you showed in your screen shot is the host's public key, not a user's public key.

 

[badincite]

Which public key have you added? What you showed in your screen shot is the host's public key, not a user's public key.

The public one from the keypair. I did get the ssh key working with putty so I know I set it up right on the esxi side.

 

[Samuel Tai]

The SSH Keypairs are only used in 1) SSH Connections for ZFS replication; and 2) in Cloud Credentials for SFTP with rclone. For shell SSH, you have to do things the old-fashioned way in CLI, with files in root's ~/.ssh directory.

 

[badincite]

The SSH Keypairs are only used in 1) SSH Connections for ZFS replication; and 2) in Cloud Credentials for SFTP with rclone. For shell SSH, you have to do things the old-fashioned way in CLI, with files in root's ~/.ssh directory.

Thanks hopefully it works this time.

 

[Samuel Tai]

@badincite, think of it this way. Anything set in the UI is for the UI's consumption. The Shell is a separate universe, and is deprecated as much as possible, as configuration changes in the Shell aren't sync'ed to the UI's middleware database, unless you're using the midclt command or the Console menu /etc/netcli.sh. Likewise, the Shell has no knowledge of the configuration database, which will overwrite manual file edits on the next boot.

Root's home directory is specifically exempted from this stomping on next boot by the configuration database, so any manual ~/.ssh files should be left alone.

 

[badincite]

@badincite, think of it this way. Anything set in the UI is for the UI's consumption. The Shell is a separate universe, and is deprecated as much as possible, as configuration changes in the Shell aren't sync'ed to the UI's middleware database, unless you're using the midclt command or the Console menu /etc/netcli.sh. Likewise, the Shell has no knowledge of the configuration database, which will overwrite manual file edits on the next boot.

Root's home directory is specifically exempted from this stomping on next boot by the configuration database, so any manual ~/.ssh files should be left alone.

How do I tell the ssh client to use the key? I grabbed the esxi.pub key and entered it into the authorized keys still asking for a password in the TrueNAS ssh client trying to get to the esxi server.

 

[badincite]

Nevermind got it with "ssh -i esxi root@192.168.1.20" thanks for the direction!