
Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tlug] SSH'ing to home with only port 80
- Date: Tue, 01 Nov 2005 10:53:31 +0900
- From: "Stephen J. Turnbull" <stephen@example.com>
- Subject: Re: [tlug] SSH'ing to home with only port 80
- References: <9c414c890510261809u778bc81aq212b7505ccbeb400@example.com> <20051028103654.573c1c95@example.com> <9c414c890510280539o41f25430x17fb74aea831fcf2@example.com> <d8fcc0800510281806x48f387cfi4e855a5a067dea7e@example.com> <9c414c890510281932h597330fy470f60b178de1ded@example.com> <1130569428.4612.16.camel@example.com> <87k6ftiuch.fsf@example.com> <1130805350.4439.8.camel@example.com>
- Organization: The XEmacs Project
- User-agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b22 (cucumber, linux)
>>>>> "Shawn" == Shawn <javajunkie@example.com> writes:
Shawn> Ok then,
Shawn> PS With http though they could sniff your password. I'd
Shawn> set it up to run https.
>> As was pointed out earlier, if http/https is being proxied, the
>> password will be converted to cleartext by the proxy.
Shawn> All's you'd have to do it PGP the password and send it as a
Shawn> file. The servlet could upload it, and decrypt it.
Unfortunately, that turns out to be useless---the intruder simply
sends the intercepted PGP file to the servlet. A sufficiently dumb
intruder might not even notice that it was PGPed, yet succeed!
Shawn> There are alternatives too.
Sure, but they require implementing the same kind of handshake that
SSH does.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
Home |
Main Index |
Thread Index