From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Permissions of /etc/sudoers
Date: Thu, 12 Feb 2009 00:01:04 +0000 [thread overview]
Message-ID: <20090212000104.4f78645e@zaphod.digimed.co.uk> (raw)
In-Reply-To: <499364B6.1050709@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
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 file?
> It's not like we have vixorgconf, vifstab. You are welcome to edit these
> files with any editor you like. Why is /etc/sudoers special?
It's no more special than /etc/passwd, which should be edited with vipw.
And it's not a specialised editor, these are just wrappers that call
$EDITOR, so you end up using the same program to edit the files, but with
a safety net. Remember that some systems restrict root access, so a
fscked /etc/sudoers could lock you out.
It's not like you HAVE to use the wrapper either, 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.
--
Neil Bothwick
Procedure: (n.) a method of performing a program sub-task in an
inefficient way by extensively using the stack instead of a GOTO.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-12 0:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 4:36 [gentoo-user] Permissions of /etc/sudoers Stroller
2009-02-09 6:43 ` Michael Hentsch
2009-02-11 23:52 ` b.n.
2009-02-11 23:57 ` [gentoo-user] " Nikos Chantziaras
2009-02-12 0:01 ` Neil Bothwick [this message]
2009-02-12 3:55 ` [gentoo-user] " Stroller
2009-02-12 0:01 ` Paul Hartman
2009-02-12 0:04 ` Neil Bothwick
2009-02-09 12:37 ` [gentoo-user] " Nikos Chantziaras
2009-02-09 13:05 ` Heiko Wundram
2009-02-09 13:15 ` Nikos Chantziaras
2009-02-09 14:20 ` Saphirus Sage
2009-02-09 14:25 ` Nikos Chantziaras
2009-02-10 8:21 ` Heiko Wundram
2009-02-09 17:02 ` Stroller
2009-02-09 18:26 ` Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090212000104.4f78645e@zaphod.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox