Allow subscriptions to have its shell set to chrooted while also having its cron jobs use a shell other than chrooted
Allow subscriptions to have its shell set to chrooted while also having its cron jobs use a shell other than chrooted.
When customer has the ability to set a custom shell for the subscription (https://docs.plesk.com/en-US/onyx/administrator-guide/server-administration/scheduling-tasks/scheduled-tasks-shell-setting.78064/#o78102) and this shell is set to CHROOT (Subscriptions > example.com > Web Hosting Access) the corresponding Schedule Tasks in the subscription cannot be run under another shell, for example /bin/bash.
For example the following command will not change the shell for that customer: plesk bin server_pref -u -crontab-secure-shell "/bin/false".
Checking upon the user will show that the shell is still CHROOT:
finger johndoe
Shell: /usr/local/psa/bin/chrootsh
Julian Bonpland
shared this idea
Thank you for your input!
Unfortunately, we have to close your request because it has not become quite popular for further implementation over the years.
--
IG
-
Hostasaurus
commented
Without this functionality, cron jobs are mostly useless if they do anything beyond a moving of files or retrieval of web content. Chroot shell tends to be used in multi-tenant environments, and in such an environment, the owner of a given subscription cannot likely place other binaries or libraries in their chroot environment. If they can't do that, then they can't create any meaningful cron job and have it actually work.
What I'm not clear on is what the purpose of the crontab-secure-shell argument actually is? It seems to accomplish nothing.