I want to use root password instead of adding my user to the list of sudoers,In Arch wiki ander Root password:Users can configure sudo to ask for the root password instead of the user password by adding "rootpw" to the Defaults line in /etc/sudoers: but that did not work for me. it asks for root password.Why do I want to do that: 1. I want to do that, I like sudo more than su -c 'some_command'. 2. sudo enables bash completion, su -c does not. 3. I don't want to add my user to sudoers list.
I found many users Suggesting alternatives and lowering the important of my need for this, when I asked this question in anther please.
Is It possible to change a process running in root-user to non-root-user by setting suid / uid / euid / gid etc... I so please instruct how, when and wat to set in order to change a process running in root-user to non-root user
I finally got magicjack working under a winxp running on a vbox. But somehow I have to login as root and run the vbox as root. otherwise if I run the vbox as a normal user, I cannot mount the magicjack usb device, it appears as a grey disabled box. I am sure this is some kind of permission issue, but not sure how to grant the permission.
It's been a few years since I last installed Ubuntu. I searched the forums and can't seem to find the answer. I want to be able to do a "su root" and have root access. I know Ubuntu wants you to do the sudo command, and I know you can really mess things up being root. I know I got this to work before. What do I need to do?
Stumped on this one. I'm trying to set up limited sudo authority on a desktop with some sensitive user data, and as an extra precaution I wanted to configure sudo to use a password other than the user's or the root's. I'm not sure how to do this. From the manual, we have a few options, such as "runaspw" or "targetpw", but none seem quite what I'm looking for.For instance, "runaspw" could be used if I created a user for nothing other than sudo(ing) purposes, but it requires you set "runas_default", which means that said user would have to have authority to execute said commands in the first place. This is workable, but seems like a lot of extra configuration for each specific command that I want to run, as well as creating some issues with simply commands such as "shutdown" or "reboot". Also, "targetpw" can be used in conjunction with a sudo(ing)-only user if I set an alias, but, again, this isn't quite what I am looking for.
Ultimately, what I am really concerned about in this situation are keystroke loggers, so I would prefer to avoid repeated entering the user or root password when performing administrative tasks. Also, I would prefer not having to create a sudo(ing)-only user as mentioned above to prevent a comprimised password resulting in an attacker being able to log into my system.
I recently re-installed my U10.04 and this time around, I added a root user and brought the permission levels of my default user to "Desktop User" as well as elevate the root permissions as explained elsewhere in these forums. Everything went fine until I wanted to "sudo" something from the Desktop User account terminal. I use Skype a lot and preferred to use the repos to get it loaded. Into synaptic where it asked me for the password. I entered the password and I was rejected. Ok, maybe I typed it in wrong. Tried again. The third time I checked in an editor to make sure I wasn't in all-caps. Third time OUT!
Switched user to root and there were no problems. Enabled the partner repos, installed Skype, as well as all the other stuff I use to run my home office. I have missed something, I know I have - perhaps a setting somewhere in the user permissions. I don't want to have to switch user every time I have to make changes to the system. Alternatively, if it's better practise to just leave my system as it is for security purposes I'm not running a server, but I'd like to have my system as secure as reasonably possible without elevating my problem to "paranoid security" level.......
I was wondering if someone had a logical reason and therefore complete, hopefully that makes total sense, for why when I install Ubuntu I cannot use the 'sudo' command either with root or user passwords. Even if I try to edit the permissions for sudoers, I still recieve an error message that says access is denied and so as the root user on my pc I don't understand why I can't put my name in the sudoers file or use the sudo command with the correct password.
I need sudo for www (apache) user to run a shell script('ip.sh' contains iptables rules) from cgi-bin directory via browser using a per script. I edit sudoers( www ALL=(ALL) NOPASSWD: ALL ),but when run the bellow command that's with err:
# sudo -u www sh /srv/www/cgi-bin/ip.sh
iptables v1.4.4: can't initialize iptables table `filter': Permission denied (you must be root) Perhaps iptables or your kernel needs to be upgraded. And:
After a few hours work I have managed to set up pptd so that my daughter can log into her account at Imperial College. My problem now is that I need to have a script that she can run if she wants to log in. She will have to invoke a couple of root commands and I do not want to give her the root password What she needs to do to set up networking is:
I've installed BOINC for first time (from suse repos). I'm worried about running BOINC as root. How can this be avoided? I'd first like to exhaust all options with the official opensuse repo version of BOINC. If I am unsuccessful, then I'll try the version from Berkeley website.
I am trying to set the umask for a process(orkaudio) which is running as the root user.This program creates dir and files and I need the umask to be 022. I have edited my /etc/bashrc -- and when i type in umask i get 0022 --- Not sure how to go about getting this resolved...
I need to run a script (which requires root privileges) on login per-user only. I want this to runtomatically so I'll add an appropriate line to .profile.A couple of questions:1 The easiest way I can think of to run the script as root is to setuid, but I know there are security concerns. Is there a better way
I use Fedora 13 LXDE and I want to know how to use sudo with my user passwordnd desactivate the root account rather than the su command like Ubuntu distribs
I need to run a command in a terminal, but cannot get root. I can in "Add Software" to install, I know and tried all the passwords I know from the install, but no show.What can I do?I tried sudo password, then typed in the space, no letters appear, but no success.TO "sudo password" after putting is my password, my username comes up and it says I am not in sudoers file.My Laptop has only one user, I know as I tried switching for a test.
following mjmwired instructions, I manually setup the sudo but I keep getting a parse error whenever sudo command is run. How do I fix this issue?I login as su -, then setup sudo using "echo 'myusername ALL=(ALL) ALL' >> /etc/sudoers". All appears OK. I exit su, and go back to myusername.
Accidentally I changed the ownership of all the directories under / to my own instead of root:root. Now I am unable to use sudo and many bad things are happening. Is there a way to revert the changes or change the permissions again to root:root or make sudo work ?
I was trying to edit a file requiring root permissions, so I used sudo. I typed the root password and it failed. This happened three times, and the process was ended. I then logged in as root (su) and was able to navigate to the file and make changes as root. Am I missing something? How would I edit the sudoers file such that this password would work? Or is there another way to log in to the sudo group to make these changes? How do I set sudo passwords?
Original HOWTO can be found at: [URL]... So the other day I was in IRC and someone had brought up a problem where they created a new Administrative user, but didnt have rights to use sudo. Looked into the problem a little bit to figure out what was wrong, and it turns out that when you create a new user through the user manager (in kubuntu, anyways. Havent tested in Gnome.) the user gets added to the adm group, however, a quick look at the sudoers file shows that its looking for users in the admin group to allow the use of sudo. So, to solve the problem we do the following: If youre on the new admin user (which Im assuming you are) use the following commands:
Code: su [insert username of old account without brackets] sudo usermod -G admin [username of new admin account without brackets] exit
Then simply logout, and then log back in (not always necessary, but the easiest way to flush the permissions.)
Code: su [insert username of old account without brackets] Means were going to Switch User to the old admin account Code: sudo usermod -G admin [username of new admin account without brackets] This simply adds the admin group to the secondary group list for the new user Code: exit Pretty self explanatory
I have some software that I need to run as root, I know I can open a terminal and su etc. if I was going to stay there to control it, that would be fine, but as the software is graphical, I would like to click it's icon, be prompted for the root password, then have it start.
I'd like to run my Apache start-up script under my own userid and not have to su over to root each time in order to run it. But if I run the script as myself I get errors on the "/usr/local/apache2/bin/apachectl start" portion (which is the 'main' purpose of the script):
(13)Permission denied: make_sock: could not bind to address [::]:80 (13)Permission denied: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs
I don't care to waste anymore time just now, or spend anymore energy just now trying to resolve *those* problems. The script works fine when I execute it logged in as root (su). I've changed the permissions to 4777 so that *me* running the script that is executed *as root* should work:
ls -l apache_up.sh -rwsrwxrwx. 1 matt matt 1114 Jul 22 16:42 apache_up.sh But it still gives the above errors. I thought changing the sticky bit would work. How do I run this script myself and have it execute the "/usr/local/apache2/bin/apachectl start" command - so that I don't have to su each time?
There is a very simple method to Run TeamViewer as a "root". This can be risky but if any users wants to running TeamViewer 5 and 6 As root then I have written a small article for the same. Requesting you to visit article and let me have some feedback or whatever comments you feel. read this article :- http://blog.ask4itsolutions.com/2011...tu-rhel-cento/ This practical performed on Red Hat Enterprise Linux 5.x, Ubuntu Desktop Edition, Fedora and CentOS
We are trying to setup fedora 12, and it has installed and now is asking for a user name on the base install, so far all we have tried will not let us in. We have, installed it a few times to see if there is a place to install the uer name or is there a root user name to use?
