sudo is a powerful command line tool that enables a “permitted user” to run a command as another user (the superuser by default), as defined by a security policy. On most if not all Linux systems, the security policy is driven by the /etc/sudoers file.
Read Also: 10 Useful Sudoers Configurations for Setting ‘sudo’ in Linux
Therefore, to run a shell script or program as root, you need to use sudo command. However, sudo only recognizes and runs commands that exist in directories specified in the secure_path in the /etc/sudoers, unless a command is present in the secure_path, you’ll counter an error such as the one below.
This will happen even if the script exists in a directory in the PATH environmental variable, because when a user invokes sudo, PATH is replaced with secure_path.
$ echo $PATH $ ls -l $ sudo proconport.sh 80
In the above scenario, the directory /home/aaronkilik/bin is in the PATH environment variable and we are trying to run the script /home/aaronkilik/bin/proconport.sh (finds process listening on a port) with root privileges.
Then we encountered the error “sudo: proconport.sh: command not found”, since /home/aaronkilik/bin is not in the sudo secure_path as shown in next screenshot.
To fix this, we need to add the directory containing our scripts in the sudo secure_path by using the visudo command by editing /etc/sudoers file as follows.
$ sudo visudo
Attention: This method has serious security implications especially on servers running on the Internet. This way, we risk exposing our systems to various attacks, because an attacker who manages to gain access to an unsecure (without superuser privileges) directory that has been added to secure_path, can run a malicious script/program with sudo command.
For security reason, do check out the following article from the sudo website explains a vulnerability relating to secure_path: https://www.sudo.ws/sudo/alerts/secure_path.html
Preferably, we can provide the absolute path to a script while running it with sudo:
$ sudo ./proconport.sh 80
That’s It! You may follow list of articles about sudo command:
- How to Run ‘sudo’ Command Without Entering a Password in Linux
- How to Keep ‘sudo’ Password Timeout Session Longer in Linux
- How to Fix “Username is not in the sudoers file. This incident will be reported” in Ubuntu
- Let Sudo Insult You When You Enter Incorrect Password
If you have any questions or thoughts concerning this article, share with us via the comment form below.
5 thoughts on “How to Run Shell Scripts with Sudo Command in Linux”
Sure would have been nice to include *HOW* to “edit with visudo” in this tutorial.
The program seems to have zero instructions, and most folks will have never used it before.
I seem to always turn to tecmint for just about everything. Thanks for all you do. This has become my main go to site.
Many thanks for the feedback, and for always following us.
Thanks – I learned something today. :)
However, hoping you might be able to advise why this occurs?
No output? Shouldn’t $secure_path be set?
secure_path is a configuration option for sudo command not the shell environment. The directories in it can only be viewed or set by opening the /etc/sudoers file.