From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Debian bug 737206 - rc shell uses insecurely /tmp
Date: Thu, 4 Dec 2014 19:20:53 -0800 [thread overview]
Message-ID: <A5F45619-2429-49EF-A6C3-52C66D28C7A0@gmail.com> (raw)
In-Reply-To: <CAJQxxwm7ijEdjSUf73yCcUFS-nRwss1=MfK01+XJpAjQ_+2zdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
+1 😄
> On Dec 4, 2014, at 7:08 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>
> Don't these people have better things to do than finding non-bugs in systems they don't understand?
>
> brucee
>
>> On 5 December 2014 at 13:33, Charles Forsyth <charles.forsyth@gmail.com> wrote:
>>
>>> On Wed, Dec 3, 2014 at 11:49 PM, Stéphane Aulery <saulery@free.fr> wrote:
>>> discovered that rc
>>> creates temporary files in an insecure way:
>>
>> rc was built for a system that made /tmp secure by not sharing it (it's always private to a user and even sometimes to a set of processes).
>> That way not every app has to try to help sustain the pretence that a shared /tmp can really be secured (+s bits, EXCL create, etc..)
>> Obviously the version for Unix will have to change its generation scheme to fit in.
>
[-- Attachment #2: Type: text/html, Size: 1770 bytes --]
next prev parent reply other threads:[~2014-12-05 3:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 23:49 Stéphane Aulery
2014-12-05 2:33 ` [9fans] " Charles Forsyth
2014-12-05 3:08 ` Bruce Ellis
2014-12-05 3:20 ` Skip Tavakkolian [this message]
2014-12-05 4:14 ` Kurt H Maier
2014-12-06 1:58 ` Bruce Ellis
2014-12-07 17:35 ` anselm
2014-12-05 3:38 [9fans] " sl
2014-12-05 9:50 ` David L. Craig
2014-12-06 0:08 ` Charles Forsyth
2014-12-06 5:22 ` lucio
2014-12-06 18:29 ` Charles Forsyth
2014-12-06 18:41 ` erik quanstrom
2014-12-06 20:56 ` Wes Kussmaul
2014-12-07 4:23 ` lucio
2014-12-07 7:31 ` erik quanstrom
2014-12-07 2:37 ` Bruce Ellis
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=A5F45619-2429-49EF-A6C3-52C66D28C7A0@gmail.com \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
/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).