9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Cc: <hangar18-general@open-forge.org>
Subject: [9fans] Re: Using 9P(2000) in Unix/Linux(/Windows)
Date: Thu, 15 May 2003 07:04:00 -0500	[thread overview]
Message-ID: <Pine.LNX.4.33.0305150650330.7974-100000@einstein.ssz.com> (raw)
In-Reply-To: <d317ff89.0305141112.7697cbde@posting.google.com>


On Thu, 15 May 2003, Anssi Porttikivi wrote:

> A practical need I have in mind and which prompted me to ask: when
> booting a CD based 'live' Linux (like Knoppix) on an arbitrary PC
> machine I'd like to mount my home directory (with all dot filed
> settings) securely over the Internet.

You'll need to create an encrypted tunnel first. Then the mount should
behave normally, except it will be even slower ;)

Since you want to use a CD you'll of course have the problem of making
sure that the keys burned on the CD are well kept. This means no loaning
of the CD to 3rd parties, and burning a seperate CD for each node you want
to boot remotely, otherwise you increase the chances of a 'known
plaintext' or 'reply' attack. You could use something similar to kerb to
pass tickets/cert's over the net instead of actual keys. This will help
against replay attacks. These sorts of things usually require sync'ed clocks
or something similar, a secure reliable shared resource (ala clock skew).

Anther approach is to use some sort of mod'ed distro (I use Trinux) and a
net-boot (eg bootp or tftp) distro. Then of course you have the 'trusted
computing' problem. If you keep up with the Cypherpunks at all, I believe
Ross Anderson has written a paper on related issues and there is a
conference of some sort coming soon on that sort of topic. Check the
archives, Ross might not be the author. The issue came up within the last
couple of weeks.

These assume that you are booting the machine from the CD.

If instead you simply want to take an existing Linux machine, slap a CD
into a drive, and then open a tunnel and mount the drive; calling that
secure at any point is hopeless with todays technology. The system is
not secrurable (ie TEMPEST/Van Eck, bus snooping, left behind swap and
malloc fragments with code/data sitting around, regular archival runs,
etc.).

You've got yourself a very! hard problem in the second case.


 --
    ____________________________________________________________________

      We are all interested in the future for that is where you and I
      are going to spend the rest of our lives.

                              Criswell, "Plan 9 from Outer Space"

      ravage@ssz.com                            jchoate@open-forge.org
      www.ssz.com                               www.open-forge.org
    --------------------------------------------------------------------



  reply	other threads:[~2003-05-15 12:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  8:57 [9fans] " Anssi Porttikivi
2003-05-14  9:25 ` boyd, rounin
2003-05-14  9:58   ` Stephen Wynne
2003-05-14 10:12     ` boyd, rounin
2003-05-14 12:10 ` Russ Cox
2003-05-14 12:29   ` Stephen Wynne
2003-05-14 13:47   ` ron minnich
2003-05-14 16:16     ` boyd, rounin
2003-05-14 15:57   ` boyd, rounin
2003-05-14 17:02     ` ron minnich
2003-05-14 17:05       ` boyd, rounin
2003-05-14 13:44 ` ron minnich
2003-05-15  9:22   ` Anssi Porttikivi
2003-05-15 12:04     ` Jim Choate [this message]
2003-05-15 13:02       ` [9fans] " Dan Cross
2003-05-15 13:08         ` boyd, rounin
2003-05-15 14:26         ` ron minnich
2003-05-15 13:59     ` [9fans] " ron minnich

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=Pine.LNX.4.33.0305150650330.7974-100000@einstein.ssz.com \
    --to=ravage@einstein.ssz.com \
    --cc=9fans@cse.psu.edu \
    --cc=hangar18-general@open-forge.org \
    /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).