From: matt <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: NAT'ing a drawterm connection
Date: Mon, 25 Aug 2003 17:05:23 +0100 [thread overview]
Message-ID: <3F4A33C3.8030003@proweb.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0308250804370.1975-100000@einstein.ssz.com>
>
>
>>a simple sniff can copy your key strokes ...
>>the auth is secure but the connection is cleartext. type away.
>>
Jim wrote :
>Yes, that is absolutely true. And we are well aware of it (sniffers are a
>regular tool for us, snoopy needs work!)
>
Russ wrote :
> No, the connection is SSL encrypted using the key established by the
auth.
This leaves me puzzled. Jim says it is cleartext and that H18 used
snoopy to verify their claims.
Does that mean that there is a faulty version of drawterm going around
or is someone talking out of their 10 gallon hat?
m
next prev parent reply other threads:[~2003-08-25 16:05 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 ` [9fans] " Jim Choate
2003-08-25 13:18 ` 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 [this message]
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=3F4A33C3.8030003@proweb.co.uk \
--to=matt@proweb.co.uk \
--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).