Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi everyone. I'm trying to allow another user to remotely run programs which require a graphical interface as me. Ideally, I'd like the other user to be able to issue a simple command like
gksudo -u userA command
without entering a password, but I can't quite figure it out. After adding the user to the sudoers file, the above command works well, but returns errors about being unable to open the display. And
sux userA command
works, but requires the other user to entire userA's password every time.
You need to set up X authentication so that the program can connect to your X windows server.
This could be as simple as using the -X option to ssh to make the remote connection. Or you might get it to work with "sudo sux userA command" (the sudo to disable the password, then run sux as root to forward X credentials for you).
works great, but I'm concerned that it's a security risk. It lets the user run any command as userA, not just the intended command. Is there another option that lets me restrict what the user can run as userA?
You can use a Runas_Spec to limit the users that they can run the command as, and use wildcards to limit the commands the user can run (remember to let the user run the command with and without sux)
Another option is to create a script to run the command as your user, and run "chmod a+rsx" on the script. It will then run suid, i.e. with the user ID of the owner of the file - but that's less good than sudo as then you can't limit who can use the file (at least, not without doing obscure things with directory ownership/permissions).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.