From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Set-uid shell scripts
Date: Thu, 8 Aug 2019 07:33:47 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.1908080724190.81938@aneurin.horsfall.org> (raw)
In-Reply-To: <40c92e85142fe7e3@orthanc.ca>
On Tue, 6 Aug 2019, Lyndon Nerenberg wrote:
>> Just to extend this thread a bit more, when did the set[ug]id bit start
>> getting turned off if the file was overwritten?
>
> I'm pretty sure that's been the case since the dawn of time.
Hmmm... I have this vague memory of V5 (which I only used for a couple of
months before we got V6) not clearing that bit, but after all these years
my memory is starting to fail me :-(
> It was certainly the case in every System V (release 0 and beyond) I
> worked with, along with many BSDs derivatives (SunOS 3+, Ultrix, etc).
> (And Xenix, which had it's own insanity that I now think selinux is
> trying to inflict on me.)
I've always thought that Xenix was insane to start with... Then again, my
first experience with it was on a 286... Now, when porting Unify, should
I use large memory model here or small memory model? Crazy.
> This has been documented in chown(2) for as long as I can remember, so
> that's a good place to start if you want to dig back through the various
> source trees.
I don't have access to the sources right now, but I'll take your word for
it; it was just a passing thought.
-- Dave
next prev parent reply other threads:[~2019-08-07 21:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 21:27 Norman Wilson
2019-08-06 8:28 ` jason-tuhs
2019-08-06 9:55 ` arnold
2019-08-06 22:48 ` Dave Horsfall
2019-08-06 22:56 ` ron minnich
2019-08-07 1:21 ` Dave Horsfall
[not found] ` <40c92e85142fe7e3@orthanc.ca>
2019-08-07 21:33 ` Dave Horsfall [this message]
2019-08-08 6:39 ` Peter Jeremy
2019-08-07 12:56 ` Chet Ramey
2019-08-07 21:40 ` Dave Horsfall
2019-08-08 5:16 ` Adam Thornton
2019-08-14 5:41 ` Efton Collins
-- strict thread matches above, loose matches on Subject: below --
2019-08-05 0:13 Noel Chiappa
2019-08-04 21:18 Norman Wilson
2019-08-04 20:18 Noel Chiappa
2019-08-04 20:29 ` Clem Cole
2019-08-04 20:42 ` Richard Salz
2019-08-04 23:58 ` Dave Horsfall
2019-08-04 7:36 Dave Horsfall
2019-08-04 7:43 ` Alec Muffett
2019-08-04 15:58 ` Noel Chiappa
2019-08-04 16:30 ` Michael Kjörling
2019-08-04 16:48 ` Alec Muffett
2019-08-04 17:48 ` Michael Kjörling
2019-08-04 19:45 ` Alec Muffett
2019-08-04 16:50 ` Rico Pajarola
2019-08-04 7:46 ` arnold
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.21.9999.1908080724190.81938@aneurin.horsfall.org \
--to=dave@horsfall.org \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).