From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] magic loopback
Date: Tue, 19 Sep 2006 20:54:58 -0400 [thread overview]
Message-ID: <ee9e417a0609191754r18e14529xbd7a2d82efc95cf@mail.gmail.com> (raw)
In-Reply-To: <70c42aec8413af91d7ac4197cefb334e@quanstro.net>
> one advantage of using 9p to encapsulate the venti rpc would be
> that authentication would be much easier. also, venti wouldn't require
> a network stack.
9p doesn't specify the authentication protocol.
you could use factotum to authenticate on the
venti connection before speaking venti and
it would be just as trivial.
it's just that no one has felt the need to make venti that
much harder to use by throwing authentication
into the mix.
if you really care about not having a network stack
you could write a network equivalent of /srv.
but really, who runs without any network stack?
> how does one protect venti from unauthorized writes if the announce
> address isn't on a real network rather than a loopback device?
at the moment, there is no such protection in venti.
on the one server where i care a little, i use ip routes
to make sure that only the hosts i want to talk to me
can talk to me.
russ
next prev parent reply other threads:[~2006-09-20 0:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 20:02 erik quanstrom
2006-09-18 3:18 ` erik quanstrom
2006-09-18 8:56 ` Richard Miller
2006-09-18 23:16 ` erik quanstrom
2006-09-19 8:04 ` Richard Miller
2006-09-19 23:07 ` erik quanstrom
2006-09-19 23:25 ` Russ Cox
2006-09-19 23:36 ` erik quanstrom
2006-09-20 0:54 ` Russ Cox [this message]
2006-09-20 9:48 ` Charles Forsyth
2006-09-20 9:55 Fco. J. Ballesteros
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=ee9e417a0609191754r18e14529xbd7a2d82efc95cf@mail.gmail.com \
--to=rsc@swtch.com \
--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).