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: NAT'ing a drawterm connection
Date: Mon, 25 Aug 2003 08:11:59 -0500	[thread overview]
Message-ID: <Pine.LNX.4.33.0308250804370.1975-100000@einstein.ssz.com> (raw)
In-Reply-To: <002e01c36b05$68bc5f50$c901a8c0@cc77109e>


On Mon, 25 Aug 2003, Bruce Ellis wrote:

> maybe you guys drawterming over open networks should consider
> the security of running a cleartext 9p connection over such a connection.
> that's what you are doing.  a simple sniff can copy your key strokes ...
> the auth is secure but the connection is cleartext.  type away.

Yes, that is absolutely true. And we are well aware of it (sniffers are a
regular tool for us, snoopy needs work!) However, before we can stick a
tunnel around it we need to understand what and how things are working.

I'd say a bug needs to be entered against Drawterm for not using the inherent
crypto of Plan 9. How long has this app been around, how many people will
use it? Poor decision not to include this when it was first crafted.

It's definitely on our 'To Do' list. Our long term plan is to have an
encrypted tunnel between each node, with each 'hub' node having a unique
key pair between it and each member node.


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




  reply	other threads:[~2003-08-25 13:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25  4:00 [9fans] " Rob Ristroph
2003-08-25  4:04 ` andrey mirtchovski
2003-08-25  5:15   ` Rob Ristroph
2003-08-25  5:22     ` andrey mirtchovski
2003-08-25  5:26       ` andrey mirtchovski
2003-08-25 12:35         ` Bruce Ellis
2003-08-25 13:11           ` Jim Choate [this message]
2003-08-25 13:18             ` [9fans] " andrey mirtchovski
2003-08-25 14:00               ` Jim Choate
2003-08-25 15:24                 ` andrey mirtchovski
2003-08-25 15:46                   ` Scott Schwartz
2003-08-25 15:55                     ` andrey mirtchovski
2003-08-25 17:40                     ` Jim Choate
2003-08-25 16:05             ` matt
2003-08-25 17:37               ` Jim Choate
2003-08-26 11:22                 ` matt
2003-08-28  0:13                   ` Bruce Ellis
2003-08-28  8:21                     ` matt
2003-08-25 13:18           ` [9fans] " Russ Cox
2003-08-25 14:02             ` [9fans] " Jim Choate
2003-08-25 17:52             ` [9fans] " Bruce Ellis
2003-08-26  0:30               ` boyd, rounin
2003-08-28  3:23               ` Russ Cox
2003-08-29  4:32         ` Rob Ristroph
2003-08-29  4:50           ` andrey mirtchovski
2003-08-25 14:53     ` matt
2003-08-26  1:53 [9fans] " Skip Tavakkolian

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.0308250804370.1975-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).