Re: [Isms] What granularity of attributes do we need for thesecuretransport?

["Randy Presuhn" <randy_presuhn at mindspring.com>]

Hi -

> From: "Juergen Schoenwaelder" <j.schoenwaelder at jacobs-university.de>
> To: "Randy Presuhn" <randy_presuhn at mindspring.com>
> Cc: <isms at ietf.org>
> Sent: Wednesday, April 09, 2008 7:39 AM
> Subject: Re: [Isms] What granularity of attributes do we need for thesecuretransport?
...
> Randy, can you check the text in <draft-ietf-isms-secshell-10.txt>?
> There is already text talking about this - if you think the text needs
> improvement, please post suggested changes.
...

You asked for it.

Existing text:
   The SSH Transport Model has no way to verify that server
   authentication was performed, to learn the host's public key in
   advance, or verify that the correct key is being used.  The SSH
   Transport Model simply trusts that these are properly configured by
   the implementer and deployer.

Add:
  Consequently, within a management domain using this transport
  model, steps outside the scope of this document MUST be taken
  to ensure that all systems within that domain have indeed been
  correctly implemented, deployed, and configured, and that those
  configurations cannot be modified in inappropriate ways.

That might be the intent of the following sections in the security
considerations section, but I must admit that they leave me with the
feeling of relying on "and then a miracle occurs", even with the level
of detail that's there.  Perhaps it's just the sheer number of assumptions.
But others in this thread have articulated those issues more clearly.

Randy

_______________________________________________
Isms mailing list
Isms at ietf.org
https://www.ietf.org/mailman/listinfo/isms