Gearing up for a password-less configuration was supposedly and easy task later then I realised that my first SSH session won’t work.
This is for obvious reason: the home folder
~/ isn’t readable - yet - not until you manually mount the folder.
By default SSH will look for
authorized_keys file at the user’s home folder henced SSH can’t read it - you’ll get
Permission denied (publickey).
One way to fix it, as suggested by others is to configure ssh and set the
AuthorizedKeysFile to a different readable path
If you allow multiple SSH users on your machine, at some stage they’ll get denied - unmounted user’s home folder etc.
Use the same fix above but use
%u user TOKEN. This will let the SSH server to open up authorized_keys file based on the current user’s username trying to connect via SSH.
$> ssh email@example.com
SSH server will look for authorized_keys file at