Support for managing autorized SSH keys
It's possible to give any system user a ~/.ssh/authorized_keys file and add public SSH keys to that file to authorize access for anyone who has the private SSH key to go with it, so users can use things like SCP/SFTP (and SSH if they have a shell configured) safely without having to use password authentication. If would be great if Plesk allowed the management of authorized SSH keys for a user.
breun
shared this idea
-
Jay Versluis
commented
That would be a great feature to have for the Migration Manager:
I wanted to migrate an Amazon EC2 instance to another server and they only allow key file logins for root. Since I don't have a password for my EC2 instance, this feature would solve my problem.
-
Matthias
commented
Why not have a Public ssh Key Field where you configure each user. That would be nice...
-
breun
commented
It seems there is a space missing in my previous comment. It should be:
----
AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2 %h/private/.ssh/authorized_keys
---- -
breun
commented
If you have already set up public key authentication and disabled password authentication make sure to NOT set 'AuthorizedKeysFile %h/private/.ssh/authorized_keys' (as per http://kb.parallels.com/en/114665 ) in /etc/ssh/sshd_config or you'll no longer be able to login as the (possibly non-Plesk) users that have authorized keys.
I recommend adding the default locations as well (AuthorizedKeysFile handles multiple locations), like this:
AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2%h/private/.ssh/authorized_keys
-
Alexei Yuzhakov
commented
Starting from PP 11.5 it will be possible to create .ssh directory and use SSH keys w/o hacks.
For older versions it's possible to use the following hack - http://kb.parallels.com/en/114665
-
Sergey Ugdyzhekov commented
Why do not use filemanager for it?