I get this message if i try to use sudo/gksudo. What causes this, how can I solve it? It has been working for years. If i remember correcttly there was a sudo update few days ago, maybe it doesnt work since then, i havent used it in the last few days.
since a recent upgrade to Mandriva 2010.1 I am not able to 'sudo' as administrator or when I use the 'root' password. I am the only user on this machine (Dell Inspiron 530S multi-booted with Window's Vista Home Premium, Ubuntu 10.4, and Mandriva 2010.1). I can get into the 'Manage Users' section of the control center by authenticating as 'root' but I can't access 'sudoers file' from command line.
I have previously set up sudo via adding my name to the wheel group and then giving full privileges to the wheel group in the sudoers file. Now I choose to learn to limit that. Had noticed the most frequent use I have of sudo is to run yum update. This got me thinking, could I remove the wheel group privileges and add the following line in sudoers to limit the privilege to simply running yum, and furthermore, make it so I could run yum without a password:
## Allow root to run any commands anywhere rootALL=(ALL) ALL Troy ALL= NOPASSWD: /usr/bin/yum
I think that would in fact work (if I understood one of the pages here, it will work). However, upon further thinking I realized that in such a case then anyone sitting at my computer could then use yum, without a password, to install or remove any file on my system � probably not a good idea. As a result I have to ask, can I tighten the privilege even further such that the only privilege so given was to run �yum update� and nothing else? (for example if they ran �yum install� it would fail). If you can do it, how?
Last, I was going to limit the privilege, time wise and try wise, by adding the following to the sudoers file:
I have a bit of a problem... I thought (for certain reasons) I would just add myself to root group and therefore gain some more rights for my account. I could sudo before... But once I gained the root group as a secondary group it says I am not in the sudoers file anymore...
Code: id uid=1000(kosta) gid=1000(kosta) groups=0(root),1000(kosta) Code: sudo ls [sudo] password for kosta:
kosta is not in the sudoers file. This incident will be reported. It is really weird and messed up. I can view sudoers file but not edit it... I can cat passwd but I can not view syslog. Is there any way to fix this without having to reboot to recovery mode? And why the heck is this happening after all?
Suddenly I am not in the sudoers file. I am not sure how to recover from this. I have no grub screen at bootup, so I can't boot into single user. I think I am going to have to boot a live version of ubuntu to start with. Is that right? What's next after that? Also, how could this happen, I haven't touched the sudoers file or added users or anything like that (well not that I am aware of) I am a little concerned that this may be the result of someone breaking in? Would this be a likely symptom?
I just installed Gutsy server. It is the only disk I can get to boot on this old PC trying to salvage. I'm at the "SERVER LOGIN" prompt. I created one user during the install. I can login as that user, but that user has "...Is not in the SudoersFile." How do I setup this user to be in the sudoers file, without having any ability to make changes to the system?
I'm running Ubuntu Server 11.04. It came time to add User to the sudoers file: so I decided to simple add User to the admin group: usermod -a -G admin user Then I used visudo to check if admin users had been set to receive sudo privileges. I uncommented the line admin ALL=(ALL) ALL. Nothing happened. I've even tried to add user directly into the sudoers file as user ALL=(ALL:ALL) ALL, but that failed too.
I need to install a package. For that I need root access. However the system says that I am not in sudoers file. When trying to edit one, it complains alike! How I am supposed to add myself to the sudoers file if I don't have the right to edit one? I have installed this system and only administrator. What can I do?
Edit: I have tried visudo already. It requires me to be in sudoers in the first place.
is it possible to do so? I mean, I want every user to be able to run '/bin/x' for example, as root without entering a password. I know the security risks, but I'm trying this in a risk-free environment which security does not matter very much.
I have a problem, I changed the own of all the etc folder, it was a mistake, but I can't change it again, now, I cant use "sudo" because root is not the own. When I try to use "sudo" this is the error: sudo: /etc/sudoers is owned by uid 1000, should be 0. so, the own is my user instead of the root. How can I change it again?
This may be a stupid (?) question, but does any one know of a patch for sudo that allows the sudoers information to be pulled from mySQL? I run multiple servers with multiple people working on them and would like a one-stop update of permissions. Yes, I could use rsync or the like, but I'm just wondering if this has been done, or could be done.
(Sorry if this is the wrong forum, I'm kinda new around here, posting wise and this seemed to fit. Feel free to move it if it's not)
I have installed debian 6 recently, and during installation I selected not to allow root login (and thereby enable my standard user to use sudo).If I check sudoers (by using visudo) my standard user is not listed anywhere, but he can still use the sudo command without any problems.Where else could this permission be stored?
I recently installed Fedora 13 "Goddard" using the graphical installer (although I prefer the 'text/ reduced graphics' option.When I start the system (after installation completes), it runs in graphical mode and presents me with a graphical login prompt. However, due to security reasons (I'm told), it won't let me log on as the root/ admin user (which is fair enough).If I log on as another user (eg : alpha, charlie or delta, for this example), I can't edit the sudoes file to add one of these users (alpha) to the file. This is because these users aren't in the file, as far as I know.
At no stage during installation was I offered an option of either setting the runlevel or adding a non-root user to the sudoers file.I have found a way to change the runlevel setting, so that is not really an issue.What I would like is either of the following :
1. A modification to Fedora's graphical installer that allows for an explicit option to set the runlevel (graphical/ command-line) and another option to add the first created non-admin user (alpha in this example) to the sudoers file.
2. Information on how to add a user to the sudoers file without adding all others (eg : alpha, but not charlie and delta, in this example).
I have read the relevant man and info pages for the su, sudo, sudoers and visudo commands, but I only got confused. (I don't know BNF/ EBNF and I would like a solution that doesn't involve having to learn these BNF dialects, although I will if I have to.)Also, I have seen solutions that show how to add all users, but not individual users, to the sudoers file. What I want is to add an individual user (if this isn't clear already).Please feel free to send me an e-mail about this post : nigel.nq.ngw[at]gmail[dot]com with the subject line "Linux Forums - Fedora 13 Add User to Sudoers"
I have a fairly complicated request The short version is, I want to set up a system so that any user can change the ownership of a certain set of files at any time without root access. I think it's possible to set up sudoers to do that, but so far I have failed miserably.I have tried setting up a wrapper script around chown, then putting that script into sudoers, but it didn't work. Here's the script and sudoers (paths changed to genericize them):
Code: #!/bin/bash #this script moves a copy of the code
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 tried several things to attempt to fix my sudoers file however it is still coming up with errors. The error says
the sudoers configuration file is set to the default as I have ran a dpkg on it, have also uninstalled and reinstalled it, and went over the configuration file ensuring it looked like the defaults I had seen online.
I need to add a user to the sudoers in my vps host and edit a couple of files and I just cannot make sense of visudo, vi or nano. The tutorials I find on the net just take too long to study and they are never complete, can someone explain what I need to do? I am running Debian 506.
Is it possible to disable all passwords in debian. I do not need any security usernames and passwords. I don't want type sudo all the times and i want free acces all the time. With debian i allways have some premission problems and why i need a password for my home computer?
1. For example today when i tried to install a file debian told me that my username is not in sudoers file. How can i fix this? 2. Is it possible to disable all passwords and asking admin premission, i dont need that kind of ??? for my home computer. (including the login screen user/password asking) And i am sorry for my grammar errors, i hope you can still understand what i have tried to say.