I have made a bash script that uses kdialog exclusively for interacting with the user. It is launched from a ".desktop" file so the user never sees the terminal. It looks 100% like a GUI app (even though it is just a bash script). It runs in KDE only (Kubuntu 12.04).
My only problem is handling password input securely and conveniently. I can't find a satisfactory solution.
The script was designed to be run as a normal user and to prompt for the password when a sudo command is first needed. In this way, most commands, those not requiring sudo rights, are run as the normal user. What happens (when the script is run from the terminal) is that the user is prompted for their password once and the default sudo timeout allows the script to finish, including any additional sudo commands, without prompting the user again. This is how I want it to work when run behind the GUI too.
The main problem is that using kdesudo
to launch my script, which is the standard GUI way, means that the entire script is executed by the root user. So file ownerships get assigned to the root user, I can't rely upon ~/
in paths, and many other things are less than ideal. Running the entire script as the root user is just a very unsatisfactory solution and I think it is a bad practice.
I appreciate any ideas for letting a user enter the sudo password just once via GUI while not running the whole script as root. Thanks.
The
-A
sudo option allows you to specify a helper program (in the SUDO_ASKPASS variable) that will ask for the password.Create a script to ask the password (myaskpass.sh):
Then insert this line at the beginning of your script:
and replace all occurences of
sudo <command>
with:You can use whatever password asking program you want instead of
zenity
. I had to encapsulate it within a script because SUDO_ASKPASS must point to a file, so it won't work with the--password
option required byzenity
.The above works like a charm if it runs from command line or if you choose Run in terminal after double click the script file in the file manager, but if you choose Run or try to launch it from a .desktop file every
sudo
will ask for the for password again.If you don't want a terminal window at all, you can store the password in a variable and pipe it to
sudo -S
. Maybe there's some security concerns, but I think it's pretty safe (read the comments on this answer).Insert this line at the beginning of your script:
and replace all occurences of
sudo <command>
with:This is based on Eric Carvalho's excellent answer. I am posting it to elaborate on the problem I encountered. Specifically, when using this the usual sudo timeout (e.g., 15 minutes) is lost. My script, which has over 50 sudo commands now prompts for the user's password 50+ times!
Here are full working example of all parts of the solution. It consists of a bash script, a "myaskpass" script as Eric suggested, and a ".desktop" file. The whole things should be 100% GUI (no terminal interaction at all), so the .desktop file is essential (afaik).
And a test script itself. This one will ask for your password twice when using this solution. (Normally, it would ask only once due to the default sudo timeout.)
The following script works via command line, desktop file or double-click, asks for the password only once, and the command pattern
sudo -Sp '' <your command here> <<<${sudo_password}
can be used multiple times anywhere in the file: