Re: [Isms] TBD secshell
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Isms] TBD secshell



--On Wednesday, January 28, 2009 05:57:58 PM -0500 David B Harrington <dbharrington at comcast.net> wrote:

Hi,

The EOP need to be updated to deal with two ports.

There is a potential issue I have not yet researched; the transport
model establishes the
connection. But the transport model does not know the operation type.
So how will it know which port to use? Of course, we have the port in
the transport address, so it can just work from that basis, but I am
not sure it knows what it needs to know to do that. In one case it
needs to act as an ssh client; in the other it needs to act as a
server

No. The entity that is establishing a new ssh session is always the ssh client.

The more interesting question is which default port to use if one is not specified in the transport address, as this depends upon whether one is sending a command or notification. How do the existing transports do this?

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

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.