• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Plesk and SSH authorized_keys

S

saschahb

Guest
hi,

normally logging into the ssh-account without password but with ssh-publickey does not work because the home directory of each plesk user is write-protected.

But for all of us who want to provide this feature to users I will show you a little quick and dirty workaround. Perhaps you'll be happy with it ;)

- Edit /etc/ssh/sshd_config (this is the debian sshd-config file. Perhaps it is called a little bit different in other linux distros)
- Add this line or change on existing one to this:
AuthorizedKeysFile %h/private/.ssh/authorized_keys
(the .ssh directory isn't expected within the root-homedir anymore. Now sshd searches within the private directory of each user)
- save and restart the sshd

to add an authorized keys file all users have to do the following:
- login to their account
- cd private
- mkdir .ssh
- chmod og-xrw .ssh (important!)
- now they have to copy their authorized_keys file to this directory

voila! it is done...

greets
Sascha
 
Hey indeed !! That's some great info !

Thanks for sharing that with the rest :)

I came across the same problem .. but never looked further to solve it.

Thanks again mate !
 
Back
Top