OpenSSH Key Storage

Nicolas Williams Nicolas.Williams at ubsw.com
Tue Feb 5 01:56:10 EST 2002


IMHO, the issue is dealing with forwarded sshd's. So the client really
ought to have a separate option for specifying the name of the expected
server host key separately from the host/port to which the client should
actually connect.

E.g.,

ssh -N the_server_I_want -l remote_user -p the_port the_host ...

No ambiguity.

Nico


On Sat, Feb 02, 2002 at 08:37:21AM +0100, Andersson, Mats wrote:
> 
> On Fri, 1 Feb 2002, Carson Gaspar wrote:
> > > it has been suggested that the server tells the client:
> > > 	lookup the hostkey under this 'name'.
> > 
> > No. Because the client can't. It doesn't have enough information. You can 
> > hack it into the client statically via the current alias mechanism, but it 
> 
> I don't see the problem here? The client (and only it) knows what
> name/port it connected to and only it knows who it expects to find there,
> the ONLY method of identifying the host I can think of is to store the
> host keys in a list searchable with host/port pairs (the "state" in the
> transport layer probably knows where its TCP endpoint is connected so it
> should be able to do the lookup right?).
> 
> Cheers,
> 
> /Mats
-- 
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.




More information about the openssh-unix-dev mailing list