• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Run bash script as root from extension

a_guy

New Pleskian
Hello,

What is the recommended way (security wise) to launch a bash script as root from a Plesk extension from customer UI?

Thanks
 
Be careful about user input validation - the ideal way is pm_Cli's callSbin function, which will escalate a script's permissions to root
 
Be careful about user input validation - the ideal way is pm_Cli's callSbin function, which will escalate a script's permissions to root

I assume you mean pm_ApiCli::callSbin.
The script runs as psaadm, shouldn't it run as root?

IndexController.php:

Code:
<?php
class IndexController extends pm_Controller_Action
{

    public function myTestAction()
    {
        $result = pm_ApiCli::callSbin("myscript.sh");
        $this->redirect('index/index');
    }
}

/usr/local/psa/admin/bin/modules/my-plugin/myscript.sh:

Code:
#!/bin/bash

systemctl stop fail2ban.service &> /tmp/mytest.txt
whoami >> /tmp/mytest.txt


and the result

Code:
[root@plesk ~]# cat /tmp/mytest.txt
Failed to stop fail2ban.service: Interactive authentication required.
See system logs and 'systemctl status fail2ban.service' for details.
psaadm

Thanks
 
Yeah, sorry.

You have to put it in the /sbin folder in your plugin. Take a look at the example extensions
 
I assume that on extension installation the sbin symlink should be created, in post-install.php.

Is there any sample code of creating a symlink from PHP using Plesk API?

Thank.
 
Back
Top