From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Allow non root users to edit files owned by root?
Date: Tue, 20 Dec 2011 13:20:52 -0500 [thread overview]
Message-ID: <4EF0D204.9070903@libertytrek.org> (raw)
In-Reply-To: <4EF0C3D3.8020504@binarywings.net>
On 2011-12-20 12:20 PM, Florian Philipp <lists@binarywings.net> wrote:
> Well, as I've said, using a/normal/ editor doesn't solve the problem
> because you can use nano for opening a shell, thereby escalating your
> privileges. You have to use rnano (or nano -R). This solution is not
> really meant for the luxury of a full blown editor with arbitrary
> arguments and capabilities. rnano doesn't read nanorc files, for
> example. If you cannot agree on a common set of safe flags, you
> shouldn't use sudo for this purpose.
Points taken from all, thanks...
I settled on requiring the -R flag for nano, and limited the files that
he can edit, so he will simply have to live with this.
Thanks all...
next prev parent reply other threads:[~2011-12-20 18:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 15:04 [gentoo-user] Allow non root users to edit files owned by root? Tanstaafl
2011-12-20 15:13 ` Michael Mol
2011-12-20 16:00 ` Florian Philipp
2011-12-20 17:03 ` Tanstaafl
2011-12-20 17:20 ` Florian Philipp
2011-12-20 18:20 ` Tanstaafl [this message]
2011-12-22 15:41 ` Tanstaafl
2011-12-22 15:46 ` James Broadhead
2011-12-20 16:51 ` Tanstaafl
2011-12-20 17:06 ` Michael Mol
2011-12-21 5:55 ` Walter Dnes
2011-12-21 19:07 ` Florian Philipp
2011-12-20 17:19 ` [gentoo-user] " Nikos Chantziaras
2011-12-22 15:44 ` Tanstaafl
2011-12-22 18:00 ` Nikos Chantziaras
2011-12-22 18:53 ` Tanstaafl
2011-12-22 19:21 ` Alan McKinnon
2011-12-22 19:33 ` Tanstaafl
2011-12-22 19:49 ` Alan McKinnon
2011-12-22 19:42 ` Nikos Chantziaras
2011-12-22 19:36 ` 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=4EF0D204.9070903@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--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