From: Chet Ramey <chet.ramey@case.edu>
To: Dave Horsfall <dave@horsfall.org>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Set-uid shell scripts
Date: Wed, 7 Aug 2019 08:56:10 -0400 [thread overview]
Message-ID: <c411365d-184d-ecfc-9e33-150efa8b2187@case.edu> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1908070840370.81938@aneurin.horsfall.org>
On 8/6/19 6:48 PM, Dave Horsfall wrote:
> It's a problem for any temporary files in a world-writable directory, hence
> the extensions to directory permissions e.g. /tmp and /var/tmp...
>
> Amusingly enough, the Mac works around this by symlinking /tmp to
> private/tmp i.e. you get your own /tmp...
/private/tmp is still word-writable with the sticky bit set. What you do
get is a private $TMPDIR, e.g.,
/var/folders/41/pgctqv8s3_301dzlcghzcbs800008y/T/
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2019-08-07 12:57 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
2019-08-08 6:39 ` Peter Jeremy
2019-08-07 12:56 ` Chet Ramey [this message]
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=c411365d-184d-ecfc-9e33-150efa8b2187@case.edu \
--to=chet.ramey@case.edu \
--cc=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).