I am having problems on a server installation (9.10) with a kind of unstable sudoers file. Logging in as a user of group admin allows only sometimes to issue sudo commands.Most of the time I am getting a "not in sudoers file" errror.
Code:
$ sudo COMMAND
[sudo] password for USER:
[code]....
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?
View 3 Replies View RelatedI 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:
# Defaults specification
Defaults:Troy timestamp_timeout=0, passwd_tries=3
Will that really work to limit the elevated privilege so I don't have elevated privileges lingering about, or is there a better way to do so?
A few minutes ago I accepted a suggestion from update-manager for restarting my system, such that some security updates could be effective. After restarting and login in as usual, I discovered that I could not use my adminstrative rights as a sudoer. To recover them I booted again, as root, and added my username in the "admin" group. Rebooting, all seemed well again. As an extra check I installed and ran 'chkrootkit' and nothing suspect was found.What could have hapenned? Just a glitch in the system? Can a user disappear from a group for nothing?What further checks can I make to be sure that my system is safe?I'm using Ubuntu Jaunty Jakalope amd64, with kernell 2.6.28-15-generic.
View 5 Replies View RelatedMy goal: I want to give users in the group "rtkprd" the ability to elevate their privileges and run a restricted shell script by using sudo. The full path to the shell script is /usr/local/bin/only_rtkprd.sh
The syntax of /etc/sudoers is giving me fits, to I've reduced my sudoers to a single log directive and a single line to enable the rtkprd group.
Code:
Defaults logfile=/var/log/sudo
%rtkprd ALL = (rtkprd) /usr/local/bin/only_rtkprd.sh
[code]....
In a recent discussion I had, I was led to believe I could use sudoers to restrict using vi (for example) for the editing of say specific config files. I know how to allow root use of vi and how to lock it down from getting to a bash prompt with NOEXEC tag,but I can't figure out how to restrict the use of vi to only edit certain files. Tutorials and howtos I have checked don't address this
View 7 Replies View RelatedI'm suspicious that the context of /etc/sudoers is wrong. During the last upgrade to Fedora 14, RPM dropped /etc/sudoers.rpmnew, which had a different context than the real sudoers file. But, when I try to get SELinux to relabel the file (using restorecon or fixfiles), it refuses to make a change.
> ls -lZ /etc/sudoers
-r--r-----. root root unconfined_u:object_r:etc_t:s0 /etc/sudoers
> matchpathcon /etc/sudoers
[code]....
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 tried several things to attempt to fix my sudoers file however it is still coming up with errors. The error says
[code]...
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.
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.
I changed my user name, and now the Terminal shows my new user name.I log in with the same user name and the same password. But after changing the username, I can't get anything done as sudo. It says that I am not in the sudoers file, and I can't get in at all. I tried sudo visudo, sudo -i, sudo -l..When, I wrote sudo -l the following came in the Terminal.How do I get into sudoers file and give my new user name ariya the root privileges. Even my old user name doesn't work at all.
View 9 Replies View RelatedHow do I add user xyz to sudoers?
View 1 Replies View RelatedI want to create a group called scripts, add www-data to that group. I then want to edit the sudoers file and tell it that the script group doesn't need a password. Where should I put this line excatly in the sudoers file?
View 2 Replies View RelatedI 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?
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.
View 9 Replies View RelatedI was planning on getting the USB to work in my 3.2.4 Oracle virtual box, and I found a post that says you have to be a part of vboxusers. I ran > sudo usermod -G vboxusers alias and then id to see that I was a part of the vboxusers group. After I installed an update which required restart. That is right! I am no longer in the /etc/sudoers file!!!
View 2 Replies View RelatedWhenever I try to run something as root using the sudo comand I get: Code: ramy is not in the sudoers file. This incident will be reported.
View 6 Replies View RelatedI am using Ubuntu 9.10 and I lost my sudo accesses for the User. So I am not able to use sudo command as I get the error,user1 is not in the sudoers file. This incident will be reported.Also I tried to login into the root usersu rootit will ask for the password(actually I dont know the password of root but after pressing enter I get the following error)su: Authentication failureI dont know how to add the user1 into the sudoers list.Also, is there any way to add the current user into admin group without using "sudo".
View 1 Replies View RelatedI'm trying to add my single user 'moreaue' to the sudoers. this user seems to be have admin privilege but is not in the sudoers:
Code:
moreaue@bloom:~$ sudo ls
[sudo] password for moreaue:
moreaue is not in the sudoers file. This incident will be reported.
moreaue@bloom:~$ su
Password:
root@bloom:/home/moreaue# adduser moreaue admin
The user `moreaue' is already a member of `admin'.
root@bloom:/home/moreaue# exit
exit
moreaue@bloom:~$ sudo ls
[sudo] password for moreaue:
moreaue is not in the sudoers file. This incident will be reported.
moreaue@bloom:~$
As you can see I can connect as root, run the adduser command which says the user is already admin... but then the user is still not a sudoer. Of course I can edit the sudoers file manually, but I wonder what is going wrong?
everytime i try to do anything with sudo i cant and this time it was extremelly costly. From now on i don't want to risk anything like this again and i need to be able to sudo.
View 2 Replies View RelatedI logged in as root and was trying to add a user to sudoers, but then when I tried to save it said that the file was write protected and couldn't be saved. However, when I returned to look at the contents of the sudoers file, they were all done. The file is now empty.
1- How can I restore the contents of the default sudoers file. (I have FC12)
2- How can I add a user (no password) to the sudoers list without this happening again?
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?
View 5 Replies View RelatedWhen I use sudo after entering password show me:
Code: Select allhooman is not in the sudoers file. This incident will be reported.
How do I add myself to the Sudoers File? When I go to use the "Sudo" command, it tells me I am not in the Sudoers File, so I have to do "su -" to bypass it for the time being. How do I add myself?
View 12 Replies View Related1.sudo command runs command as root,is that our name should be mentioned in the sudoers file of root?i got the error like this-"sandyain is not in the sudoers file.This incident will be reported."so what is that mean?
View 4 Replies View RelatedHow do I add a user in a sudoers file.
View 6 Replies View RelatedI'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.
View 3 Replies View RelatedI wanted to do an installation from my user login so I typed
sudo make install
then it says
<my_user_loggin> is not in the sudoers file. This incident will be reported.
How to correct this matter...
In my sudoers file, there are lines that begin with #, lines that begin with % and lines that begin with neither. The # is definitely being used to comment out lines, but what does the % do? Is it a comment marker too?
View 2 Replies View RelatedRecently I edited sudoers file and did typing error. Now neither I can do sudo nor change it.
Code:
sudo visudo -c
>>> sudoers file: syntax error, line 8 <<<
How I can get correct the sudoers file?
