Results 1 to 4 of 4
Hi. This might be obvious to somebody, but I'm stuck. I have the following problem(s) and I'm not sure how to solve it/ them :
I recently installed Fedora 13 ...
- 07-16-2010 #1
Fedora 13 : Add User to Sudoers
Hi. This might be obvious to somebody, but I'm stuck. I have the following problem(s) and I'm not sure how to solve it/ them :
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 :
from a post by devils_casper :
> in GRUB screen, select Fedora title and press 'e'. add 3 at the end of 'kernel' line and press 'b' to boot up. this will drop you on command line login prompt. log in as root and execute this command.
>
> # system-config-display
> # startx
>
> to configure display settings, resolutions etc and to load GUI.
>
I reckon editing /boot/grub/menu.lst will achieve the same or similar results.
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"
Thankyou.
- 07-17-2010 #2forum.guy
- Join Date
- May 2004
- Location
- arch linux
- Posts
- 18,099
This is the HowTo that I always use when needing help with sudo/sudoers and I believe it describes how to go about setting up what you want to do:
Sudo Howto
Hope it helps.oz
→ new members/users: read this first | new member faq
→ no private messages requesting computer support - post them on the forums!
→ please use the "report post" button to alert our forum admins to problematic posts rather than responding to them yourself.
- 07-19-2010 #3
What is the Point of the su Command in a Secure System?
@Ozar : Thank you very much!
I have spent considerable time on trying to resolve this annoying 'security feature' of Fedora's ^ and I somehow missed the page you link to.
It answers most of the questions that I have about su, sudo, visudo and sudoers. I would like to know if making su an alias for sudo would have any adverse effects (such as 'breaking' shell scripts that use su). I fail to see the use of su in a truly secure system if my understanding of su - is correct (that it allows all users to run commands as the root user, without requiring the user to enter a password).Code:alias su=sudo
^ Has the Fedora Project joined Novell in comitting 'economic' suicide by forming an alliance with Microsoft (seems like it here) or are appearances truly deceptive?
- 07-19-2010 #4Just Joined!
- Join Date
- May 2007
- Posts
- 72
I would like to know if making su an alias for sudo
Code:
alias su=sudo
would have any adverse effects (such as 'breaking' shell scripts that use su). I fail to see the use of su in a truly secure system if my understanding of su - is correct (that it allows all users to run commands as the root user, without requiring the user to enter a password).
su normally asks for the root password, so if you have a password (and didn't just hit the return key when you were asked for it during installation) it won't run without the pw being entered. Its weakness is that it gives root privileges indefinitely, so if you forget or walk away from the computer another user or perhaps process could run as root, which is why some OS's have sudo.


Reply With Quote
