1995-07-14 - Re: Ssh security hole?

Header Data

From: “Perry E. Metzger” <perry@imsi.com>
To: Tatu Ylonen <ylo@cs.hut.fi>
Message Hash: dc5c0bfd5df36b58b1d963f58232bde89ab49a5b17b0e544f7a57c1e049ffac1
Message ID: <9507140202.AA13400@snark.imsi.com>
Reply To: <199507132303.CAA18383@shadows.cs.hut.fi>
UTC Datetime: 1995-07-14 02:04:34 UTC
Raw Date: Thu, 13 Jul 95 19:04:34 PDT

Raw message

From: "Perry E. Metzger" <perry@imsi.com>
Date: Thu, 13 Jul 95 19:04:34 PDT
To: Tatu Ylonen <ylo@cs.hut.fi>
Subject: Re: Ssh security hole?
In-Reply-To: <199507132303.CAA18383@shadows.cs.hut.fi>
Message-ID: <9507140202.AA13400@snark.imsi.com>
MIME-Version: 1.0
Content-Type: text/plain



Tatu Ylonen writes:
> (I'll forward your message to a couple of lists where it might be
> of interest; the original message is at end.)
> 
> I think you are right in your analysis.  There is indeed a problem
> with RSA authentication.  Basically what this means is that if you log
> into a corrupt host, that host can at the same time log into another
> host with your account (by fooling you to answer to the request)
> provided that you use the same RSA identity for both hosts.
> 
> A workaround is to use a different identity for each host you use.
> The default identity can be specified on a per-host basis in the
> configuration file, or by -i options.

Might I suggest that a better solution would be to adapt the station
to station protocol, or, even better, Photuris...

.pm





Thread