From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Copying pushtls(2)
Date: Fri, 8 Aug 2003 09:51:21 -0400 [thread overview]
Message-ID: <a483160d5836435ca9fa6fc74a78754f@plan9.bell-labs.com> (raw)
In-Reply-To: <3ce92a5b134d67c8bdf471134962e8e4@vitanuova.com>
I'm not sure which message you are responding to. It is definitely
true that devsrv, devtls, and devssl cannot have fd's passed to them
by remote systems.
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.
Proof that a useful hack is still a hack and probably a bad idea.
next prev parent reply other threads:[~2003-08-08 13:51 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 [this message]
2003-08-08 13:51 ` Lucio De Re
2003-08-08 14:19 ` David Presotto
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=a483160d5836435ca9fa6fc74a78754f@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).