OpenSSH Key Storage

[Nicolas Williams]

On Mon, Feb 04, 2002 at 04:40:21PM +0100, Andersson, Mats wrote:
> 
> On Mon, 4 Feb 2002, Nicolas Williams wrote:
> > 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
> 
> Ok, I thought the issue was with different servers on different ports on
> same host. Forwarded servers seems to be handled by the alias function
> which is in openssh allready? (forwarded servers != servers at different
> ports).

Sorry, what exactly is the difference, from the client's point of view,
between forwarded servers and multiple servers on one host with
different port numbers?

If anything, the expectation that known host key names relate to
hostnames as resolvable through the name services (e.g., DNS) is the
thing that leads to any difference.

I.e., the multiple servers on one host on multiple ports will all be
expected to have the same name because it's one host(*).

But the name is really a functional name. So, allowing a separation of
host key name from hostname/port makes sense. If the ports in question
are dynamically obtained for different runs then what other option is
there? Dynamically updating known host keys / aliases?

(*) ignore multi-homing for this.

> Cheers,
> 
> /Mats
> 


Cheers,

Nico
-- 
-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.