• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

How to limitate shells?

H

hansg

Guest
Hello,

I have just a short question.
I want to limit the shell selection in Plesk 8.6. So that admin could only select scponlyc as a valid shell. All other shells includng the chrooted bash etc, should be marked as non selectable, invisible or should link to scponlyc.

Anyone has a clue how to do this?

Best regards

HansG
 
The admin can do anything (including running commands as root). You cannot limit admin's powers.
 
i already fixed it. i run a script on phosting update, so the shell of any user with shell != scponlyc will set up a scponlyc shell and usermod to this shell, /bin/false will remove the chroot env and set the shell to /bin/false

little dirty fix, but it isn't the first for plesk -.-

thanks anyway
 
Back
Top