Michael Hentsch ha scritto:
The file /etc/sudoers should always be edited with visudo. visudo uses
file locking, provides basic sanity checks and checks for parse errors.
This always made me crazy.
Why, why, why should I use a specialized editor to edit a system file?
It's not like we have
On Thu, 12 Feb 2009 00:52:22 +0100, b.n. wrote:
The file /etc/sudoers should always be edited with visudo. visudo uses
file locking, provides basic sanity checks and checks for parse
errors.
This always made me crazy.
Why, why, why should I use a specialized editor to edit a system
On Wed, Feb 11, 2009 at 5:52 PM, b.n. brullonu...@gmail.com wrote:
Michael Hentsch ha scritto:
The file /etc/sudoers should always be edited with visudo. visudo uses
file locking, provides basic sanity checks and checks for parse errors.
This always made me crazy.
Why, why, why should I use
On Wed, 11 Feb 2009 18:01:36 -0600, Paul Hartman wrote:
I guess an error in sudoers could allow the whole world to use sudo,
and someone decided to give this special cushion to this program and
none of the others that can also ruin your system in various other
ways. :)
You could also lock
On 12 Feb 2009, at 00:01, Neil Bothwick wrote:
... there's nothing to stop
you using any editor you like, directly, and it's the best choice if
you
want to be free to screw up the file.
It's the Unix way!
Stroller.
Hi there,
I'm just in the process of setting up my lovely new system :D, in the
very first post-install steps.
I install sudo, give my user wide sudo rights and then set
PermitRootLogin no in /etc/ssh/sshd_config.
(Critique of this measure welcomed).
Anyway, as root I started to edit
Stroller schrieb:
Hi there,
I'm just in the process of setting up my lovely new system :D, in the
very first post-install steps.
I install sudo, give my user wide sudo rights and then set
PermitRootLogin no in /etc/ssh/sshd_config.
(Critique of this measure welcomed).
Anyway, as root I
7 matches
Mail list logo
