public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Allow non root users to edit files owned by root?
Date: Thu, 22 Dec 2011 13:53:43 -0500	[thread overview]
Message-ID: <4EF37CB7.1080400@libertytrek.org> (raw)
In-Reply-To: <jcvr6h$8ir$1@dough.gmane.org>

On 2011-12-22 1:00 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
> On 12/22/2011 05:44 PM, Tanstaafl wrote:
>> On 2011-12-20 12:19 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
>>> If you allow someone to edit root owned files, you're practically giving
>>> him root access.
>>
>> Well, yeah, but only on those defined files...
>
> root access is global. You can't limit it. root is root, the all
> powerful Unix being. Period :-)

Ummm... then what is the purpose of sudo??

If I add the following line to sudoers:

%sudoroot       ALL=(root)NOPASSWD:/bin/chmod /var/www/localhost/htdocs/*

Are you saying that this does NOT limit anyone in the sudoroot group to 
*only* be able to run the chmod command, and only on files located in 
/var/www/localhost/htdocs?

> Then you put the files in a special group and make them g+w, and add the
> affected users to that group. Then they will able to write to those
> files. If you want to give them write access to a whole directory, you
> put the directory in the group and make it g+w. This is how it's
> traditionally been done in Unix for ages, and it's extremely easy to set
> up.

Yeah, I think I got a little tunnel vision trying to do this with sudo.



  reply	other threads:[~2011-12-22 18:55 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
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 [this message]
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=4EF37CB7.1080400@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