9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rahul Murmuria <rahul.is.also@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Question on /net with respect to anonymity
Date: Wed, 17 Mar 2010 03:20:24 -0400	[thread overview]
Message-ID: <9511f83e1003170020r96e5355gc844691ba94df20c@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.64.1003161807130.27466@malasada.lava.net>

On Wed, Mar 17, 2010 at 12:08 AM, Tim Newsham <newsham@lava.net> wrote:
>> However, the absence of ipfilters / iptables means, the gateways
>> really have no history information and no control over who is having
>> access to either of its interfaces.
>
> If I mounted my gateway's /net onto my machine, I would expect
> that the gateway would do no extra filtering on my connections
> than it did on any of its own connections. That's a feature,
> not a bug.
>

Ditto. I did not intend to mean anything contrary to that. My interest
is only to explore the networking aspects (if any), of using /net with
9P, as against the existing POSIX compliant networks we have, on
fronts like anonymity, firewalling and the like. It is important to
know that, if I am working to have /net on Linux.. because at the
moment, I have no reason to believe that there is any use at all in
doing so, apart from enabling the "compiled on/for Plan 9" a.out
binaries to find the /net (which they assume to be available
everytime... on Plan 9 systems) when loaded on a Linux kernel with
Glendix patches.

> Am I misunderstanding what you're saying?
>
>> Rahul Murmuria
>
> Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
>
>



--
Rahul Murmuria



      reply	other threads:[~2010-03-17  7:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17  0:17 Rahul Murmuria
2010-03-17  4:08 ` Tim Newsham
2010-03-17  7:20   ` Rahul Murmuria [this message]

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=9511f83e1003170020r96e5355gc844691ba94df20c@mail.gmail.com \
    --to=rahul.is.also@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).