From: J Sloan <joe@tmsusa.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: suid bit on directories
Date: Tue, 21 May 2002 11:35:07 -0700 [thread overview]
Message-ID: <3CEA935B.2080005@tmsusa.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020521140333.1427C-100000@gatekeeper.tmr.com>
Bill Davidsen wrote:
>On Mon, 20 May 2002, Dax Kelson wrote:
>
>
>
>>On Mon, 20 May 2002, Dax Kelson wrote:
>>
>>
>>
>>>Example 1:
>>>
>>>/home/bob/public_html
>>>
>>>public_html is user/group bob/httpd
>>>
>>>the perms are 2770
>>>
>>>
>>I meant 4770 since we are discussing a hypothetical SUID directory.
>>
>>
>
>I would expect public_html to be 4775 or 4771 if it's to be any use at all. Otherwise why have it?
>
>
Yes, it would have to have httpd group ownership
or it would be totally inaccessible - and it would
be difficult for a non-root user to assign such grp
ownership....
Joe
next prev parent reply other threads:[~2002-05-21 18:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-18 8:34 suid bit on directories Michael Hoennig
2002-05-18 8:52 ` Cedric Ware
2002-05-18 10:34 ` Michael Hoennig
2002-05-19 1:12 ` jw schultz
2002-05-20 13:04 ` Jesse Pollard
2002-05-20 13:24 ` Michael Hoennig
2002-05-20 14:03 ` Jesse Pollard
2002-05-20 14:53 ` Michael Hoennig
2002-05-20 18:12 ` dean gaudet
2002-05-21 17:48 ` Bill Davidsen
2002-05-20 19:28 ` Jesse Pollard
2002-05-20 20:58 ` Miquel van Smoorenburg
2002-05-20 21:15 ` Michael Hoennig
2002-05-21 18:03 ` Bill Davidsen
2002-05-22 4:44 ` Michael Hoennig
2002-05-21 3:49 ` Dax Kelson
2002-05-20 15:53 ` Bill Davidsen
2002-05-20 19:17 ` Albert D. Cahalan
2002-05-20 20:17 ` Jesse Pollard
2002-05-21 3:28 ` Dax Kelson
2002-05-21 3:58 ` Dax Kelson
2002-05-21 18:04 ` Bill Davidsen
2002-05-21 18:35 ` J Sloan [this message]
2002-05-20 15:42 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2002-05-21 13:34 Jesse Pollard
2002-05-21 13:34 Jesse Pollard
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=3CEA935B.2080005@tmsusa.com \
--to=joe@tmsusa.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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