Sudo

big_gie · 2007-06-26 23:27:42

I prefer using sudo on my computer without anybody else using it. That way, to execute a command which could break something I need to add "sudo" before.
As KerowynM said, if you _always_ add sudo before the command, its useless.

cry0x · 2007-06-28 21:24:33

I love sudo. Besides package management, once my system is setup, I don't really do much as root. So, root is disabled, and my user account has a secure password. If I need to do a whole batch of commands as root, just sudo -s.

Like many have said, sudo prevents me from forgetting to logout as root.

Last edited by cry0x (2007-06-28 21:25:11)

Ikarus · 2007-07-11 08:26:41

As long as i'am the only one who uses my box i stay with su. For multiple users i would prefer sudo.

shining · 2007-07-11 08:59:50

don't know how stupid that is, but I use sudo to keep using the same configurations, eg ~/.zshrc , ~/.vimrc , ... when doing privileged operations,
like installing a package (zsh completion) or editing a file in /etc/ (vim config), etc

mosor · 2007-07-15 10:26:42

The fastest and most productive for myself is to disable root loogin, setup sudo to ask for no password, alias 'sudo' to 's', and just prefix all commands that require root access with 's'. That way I can use my zsh, vim, etc... settings. Used together with zshs' reverse history search feature, I can't remember the last time I typed a command longer that 2 or 3 letters .

Ankka · 2007-07-15 12:26:38

I have set up sudo almost like ubuntu has: no root account and sudo asks for a password.

Nice and secure. If I want to do something with sudo, I need to put my password in.. and have that second of time to think what I'm doing.

iphitus · 2007-07-15 12:53:16

skymt wrote:

The_ouroboros wrote:
skymt wrote:
I've disabled the timeout completely in my sudo configuration file.
how you did it?
1. Log in as root (su, sudo -s, whatever).
2. # cp /etc/sudoers /etc/sudoers.temp
3. Edit /etc/sudoers.temp with your favorite editor
4. Add this line under the "Defaults specification" comment:
Defaults    timestamp_timeout=0
5. Save the file, quit your editor
6. # visudo -c -f /etc/sudoers.temp
7. # mv -f /etc/sudoers.temp /etc/sudoers
This method of editing the file is more convoluted than it needs to be, but sudo breaks if there's an error in the sudoers file, so it's best to err on the side of caution.

which is why you're meant to edit the file by running "visudo" -- not editing manually -- as it checks for errors in the file, and alerts you.

James

finferflu · 2007-07-15 17:57:50

mosor wrote:

The fastest and most productive for myself is to disable root loogin, setup sudo to ask for no password, alias 'sudo' to 's', and just prefix all commands that require root access with 's'. That way I can use my zsh, vim, etc... settings. Used together with zshs' reverse history search feature, I can't remember the last time I typed a command longer that 2 or 3 letters .

How did you manage to disable the password? I tried to follow the Arch wiki, but it keeps asking me for a password every time...

Thanks

shining · 2007-07-15 18:52:09

finferflu wrote:

mosor wrote:
The fastest and most productive for myself is to disable root loogin, setup sudo to ask for no password, alias 'sudo' to 's', and just prefix all commands that require root access with 's'. That way I can use my zsh, vim, etc... settings. Used together with zshs' reverse history search feature, I can't remember the last time I typed a command longer that 2 or 3 letters .
How did you manage to disable the password? I tried to follow the Arch wiki, but it keeps asking me for a password every time...
Thanks

hmm? It's already in there :

# Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL

You just have to decomment that line using visudo.

skymt · 2007-07-15 19:08:17

iphitus wrote:

which is why you're meant to edit the file by running "visudo" -- not editing manually -- as it checks for errors in the file, and alerts you.
James

visudo uses the vi editor by default, which many users don't know. It doesn't even respect the $EDITOR env variable, instead using a variable in the sudoers file. This effectively locks out newbies, as you have to use vi to tell visudo to open an editor other than vi (catch-22!). Step 6 in the method I laid out uses visudo to do a syntax check before committing the changes by overwriting the sudoers file, so there would be no real benefit to just using visudo to edit it.

finferflu · 2007-07-15 20:26:08

@ shining

Thanks for you help... I was so busy following the wiki that I completely overlooked the sudoers file...

Arch Linux

#26 2007-06-26 23:27:42

Re: Sudo

#27 2007-06-28 21:24:33

Re: Sudo

#28 2007-07-11 08:26:41

Re: Sudo

#29 2007-07-11 08:59:50

Re: Sudo

#30 2007-07-15 10:26:42

Re: Sudo

#31 2007-07-15 12:26:38

Re: Sudo

#32 2007-07-15 12:53:16

Re: Sudo

#33 2007-07-15 17:57:50

Re: Sudo

#34 2007-07-15 18:52:09

Re: Sudo

#35 2007-07-15 19:08:17

Re: Sudo

#36 2007-07-15 20:26:08

Re: Sudo

Board footer