From: Jim Choate <ravage@einstein.ssz.com>
To: <hangar18-general@open-forge.org>
Cc: <9fans@cse.psu.edu>
Subject: [9fans] Re: NAT'ing a drawterm connection (fwd)
Date: Mon, 25 Aug 2003 13:07:22 -0500 [thread overview]
Message-ID: <Pine.LNX.4.33.0308251303000.1975-100000@einstein.ssz.com> (raw)
Hi,
<sigh>
We are currently looking at using ssh to make an initial connection and
then push a ppc connection through that.
We'll update the H18 Configure How To as we make progress.
-- --
ravage@ssz.com jchoate@open-forge.com
www.ssz.com www.open-forge.com
---------- Forwarded message ----------
Date: Tue, 26 Aug 2003 03:52:52 +1000
From: Bruce Ellis <brucee@chunder.com>
Reply-To: 9fans@cse.psu.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] NAT'ing a drawterm connection
NO. There is no devssl in drawterm. Not hard but not done.
And and a firewall doesn't stop the sniff. Type away.
> No, the connection is SSL encrypted using the key established by the auth.
>
> Russ
reply other threads:[~2003-08-25 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.0308251303000.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).