![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
>>>>> "Juergen" == Juergen Schoenwaelder <j.schoenwaelder at iu-bremen.de> writes:
Juergen> 2) It is important to talk about ssh and to not reduce the problem to
Juergen> just TCP. As far as I understand ssh, authentication is not
Juergen> symmetric because ssh has a clear buildin client/server role
Juergen> (servers authenticated via host keys while clients are
Juergen> authenticated via passwords or publickey mechanisms).
Juergen> So in the context of ssh, it does have quite some impact who
Juergen> establishes the transport connection. (Unless there is a "turn"
Juergen> feature in _ssh_. I am not aware of such a mechanism, but I am
Juergen> happy to learn.)
Authentication is sometimes symmetric; it is not in the case of
passwords. For authentication methods like public key or GSS, it is reasonably symmetric.
--Sam
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.