ESXi is a funny beast when it comes to SSH keys, and there’s a lot of misinformation about on how to configure them persistently, not to mention security FUD.
ESXi uses an in-memory only filesystem for the bootable portion of it, so following the published guide will only get you so far. You’ll find that after rebooting, your changes will no longer be there.
You can work around this limitation by rebuilding the keys on boot using
/etc/rc.local.d/local.sh. Somewhere before the
exit 0, add a modified
version of the following:
mkdir -p /etc/ssh/keys-<username> echo "ssh-rsa AAAAB3..." > /etc/ssh/keys-<username>/authorized_keys chmod 700 -R /etc/ssh/keys-<username> && chmod 600 /etc/ssh/keys-<username>/authorized_keys chown -R <username> /etc/ssh/keys-<username>
<username> and the value of the public key are replaced with actual
Once you’ve done this, ensure it’s backed up by running:
auto-backup.sh runs every hour and backs up certain known
files which are marked with the “sticky bit” (
chmod +t file). These are then
restored on reboot.
auto-backup.sh only knows about certain files, so we’re
adding this to one it knows about.
This pattern can used in a similar way for other settings which need to stay around after reboots.
VMware seem to not recommend enabling SSH by default, and that’s fine. If you disagree with that, you can enable it inside the Web UI by going to “Manage”, “Services” finding “TM-SSH” and selecting “Actions”, “Policy”, enable “Start and stop with host”.