From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] rm command
Date: Fri, 27 Apr 2018 14:14:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1804271412490.38781@frieza.hoshinet.org> (raw)
In-Reply-To: <alpine.BSF.2.21.999.1804280201170.62425@aneurin.horsfall.org>
On Sat, 28 Apr 2018, Dave Horsfall wrote:
> On Wed, 25 Apr 2018, Noel Chiappa wrote:
>
>> On early PDP-11 Unixes, 'rm' is an ordinary program, and 'rmdir' is
>> setuid-root, since it has to do special magic (writing into directory
>> files, etc). Given that, it made sense to have 'rm' run with the least
>> amount of privilege needed to do its job.
>
> I am constantly bemused by the number of "setuid root" commands, when a
> simple "setgid whatever" will achieve the same task.
>
> My mantra has always been: "If you think you need setuid root, then you are
> probably thinking wrong."
>
> My favourite here is the "ps" command:
>
> On my FreeBSD server:
>
> % ls -l /bin/ps
> -r-xr-xr-x 1 root wheel 35640 Oct 15 2017 /bin/ps
>
> On my crappy MacBook:
>
> % ls -l /bin/ps
> -rwsr-xr-x 1 root wheel 51200 Jul 15 2017 /bin/ps
>
> (I didn't check my Penguin box, because I don't think that I'll like what
> I'll see.)
>
> -- Dave
>
Debian 9:
nicci at jesustheasus:~$ ls -l $(which ps)
-rwxr-xr-x 1 root root 129336 Nov 22 2016 /bin/ps
Debian 8 kFreeBSD:
[usotsuki at licca ~]$ ls -l $(which ps)
-rwxr-xr-x 1 root root 93088 Mar 6 2015 /bin/ps
-uso.
next prev parent reply other threads:[~2018-04-27 18:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 22:17 Noel Chiappa
2018-04-27 16:26 ` Dave Horsfall
2018-04-27 16:58 ` Ian Zimmerman
2018-04-27 18:14 ` Steve Nickolas [this message]
2018-04-27 18:17 ` Pete Wright
2018-04-28 16:33 ` Michael Kjörling
2018-04-28 18:01 ` Ian Zimmerman
2018-04-28 18:51 ` Derek Fawcus
-- strict thread matches above, loose matches on Subject: below --
2018-04-27 16:42 Noel Chiappa
2018-04-26 2:19 Doug McIlroy
2018-04-26 9:41 ` Ralph Corderoy
2018-04-25 20:22 Eric Blood
2018-04-25 21:23 ` Ralph Corderoy
2018-04-25 21:33 ` John P. Linderman
2018-04-25 21:53 ` William Corcoran
2018-04-25 21:58 ` Derek Fawcus
2018-04-25 22:09 ` Ralph Corderoy
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=alpine.BSF.2.02.1804271412490.38781@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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;
as well as URLs for NNTP newsgroup(s).