From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Copying pushtls(2)
Date: Fri, 8 Aug 2003 10:19:42 -0400 [thread overview]
Message-ID: <912569f85725304c0ac33d349a74b8a3@plan9.bell-labs.com> (raw)
In-Reply-To: <20030808155134.G1666@cackle.proxima.alt.za>
On Fri Aug 8 10:07:35 EDT 2003, lucio@proxima.alt.za wrote:
> On Fri, Aug 08, 2003 at 09:51:21AM -0400, David Presotto wrote:
> >
> > I agree that I screwed up when I copied the devsrv semantics into
> > devtls and devssl. It's convenient but not distributable. In
> > fact, now that I think of it, its probably a security hole since
> > exportfs doesn't really know what's going on under it and you can
> > hijack its fd's through #D, #s, and #a.
> >
> Hm, it's hard to live without #s, what does it need not to be a
> security risk? Some rendez-vous rules like in changing the group of a
> file?
That's not the problem. It's the fact that you can create in /srv.
next prev parent reply other threads:[~2003-08-08 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 12:35 Lucio De Re
2003-08-08 13:29 ` David Presotto
2003-08-08 13:39 ` Lucio De Re
2003-08-08 13:42 ` C H Forsyth
2003-08-08 13:51 ` David Presotto
2003-08-08 13:51 ` Lucio De Re
2003-08-08 14:19 ` David Presotto [this message]
2003-08-08 14:32 ` Lucio De Re
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=912569f85725304c0ac33d349a74b8a3@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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).