From: "Russ Cox" <rsc@swtch.com>
To: lucio@proxima.alt.za,
"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] RFNOMNT
Date: Sun, 4 Jan 2009 09:04:00 -0800 [thread overview]
Message-ID: <dd6fe68a0901040904p20666ac7sd141ee70b9ad28c4@mail.gmail.com> (raw)
In-Reply-To: <191db05806ff4757bc93d5bc04cfeef9@proxima.alt.za>
I agree that it would be nice if the exceptions were
documented in the man page. They are quite nicely
documented in the code, though:
/*
* noattach is sandboxing.
*
* the OK exceptions are:
* | it only gives access to pipes you create
* d this process's file descriptors
* e this process's environment
* the iffy exceptions are:
* c time and pid, but also cons and consctl
* p control of your own processes (and unfortunately
* any others left unprotected)
*/
n = chartorune(&r, up->genbuf+1)+1;
/* actually / is caught by parsing earlier */
if(utfrune("M", r))
error(Enoattach);
if(up->pgrp->noattach && utfrune("|decp", r)==nil)
error(Enoattach);
Russ
next prev parent reply other threads:[~2009-01-04 17:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 7:08 RFNOMNT Russ Cox
2009-01-04 12:21 ` [9fans] RFNOMNT lucio
2009-01-04 17:04 ` Russ Cox [this message]
2009-01-04 18:27 ` lucio
2009-01-04 16:12 ` erik quanstrom
2009-01-05 1:01 ` Roman V. Shaposhnik
2009-01-05 4:18 ` Skip Tavakkolian
2009-01-05 4:01 ` lucio
2009-01-05 5:48 ` Russ Cox
2009-01-07 6:24 ` [9fans] RFNOMNT and/or "least privilege" Dave Eckhardt
2009-01-07 13:15 ` sqweek
2009-01-08 19:29 ` Roman V. Shaposhnik
2009-01-08 19:57 ` Charles Forsyth
2009-01-08 19:45 ` Nathaniel W Filardo
2009-01-08 20:11 ` Charles Forsyth
2009-01-08 21:29 ` Roman V. Shaposhnik
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=dd6fe68a0901040904p20666ac7sd141ee70b9ad28c4@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).