AWS transfer: AWS Transfer Family NLB doc: clarify PROXY protocol v2 SSH client compatibility
Summary
Rewrote the explanation of why some SSH clients stall with PROXY protocol v2 (clients supporting SSH protocol version 1 waiting for the server identification string), reordered and expanded the compatible-client version table, and updated the RFC 4253 link text.
Security assessment
The content addresses connection-stall/compatibility behavior of PROXY protocol v2 with SSH clients, not authentication, encryption, or exposure. The mention of SSH protocol version 1 is explanatory context for the stall, not a security recommendation.
Evidence
+Some older SSH clients wait to receive the server's SSH identification string before they send their own. Clients that still support SSH protocol version 1 do this so that they can choose a protocol version based on the server's identification string. When PROXY protocol v2 is enabled on an NLB target group, the NLB doesn't deliver the server's identification string to the client until the client sends data. These clients connect and wait for the server's identification string, so they never send their own, and the connection stalls until it times out.
Diff
diff --git a/transfer/latest/userguide/working-with-nlb.md b/transfer/latest/userguide/working-with-nlb.md index 34d838b..6bc9738 100644 --- a//transfer/latest/userguide/working-with-nlb.md +++ b//transfer/latest/userguide/working-with-nlb.md @@ -37 +37 @@ When you enable PPv2, the client's source IP address becomes available in the fo -After the TCP connection is established, both the client and the server send an SSH identification string as their first data. This string identifies their SSH protocol and software versions, for example `SSH-2.0-OpenSSH_10.3`. For more information, see the [SSH transport layer protocol (RFC 4253)](https://datatracker.ietf.org/doc/html/rfc4253#section-4.2). Some older SSH clients wait to receive the server's SSH identification string before they send their own. When PROXY protocol v2 is enabled on an NLB target group, the NLB doesn't deliver the server's identification string to the client until the client sends data. These clients connect and wait for the server's identification string, so they never send their own, and the connection stalls until it times out. +After the TCP connection is established, both the client and the server send an SSH identification string as their first data. This string identifies their SSH protocol and software versions, for example `SSH-2.0-OpenSSH_10.3`. For more information, see [SSH transport layer protocol (RFC 4253)](https://datatracker.ietf.org/doc/html/rfc4253#section-4.2) on the IETF Datatracker website. @@ -39 +39,3 @@ After the TCP connection is established, both the client and the server send an -SSH clients that wait to receive the server's SSH identification string before they send their own fail to complete the connection when PROXY protocol v2 is enabled. The following table lists common SSH clients and the minimum version of each that is known to be compatible with PROXY protocol v2. This list isn't comprehensive. If you use a client that isn't in this table, test its compatibility before you enable PROXY protocol v2. +Some older SSH clients wait to receive the server's SSH identification string before they send their own. Clients that still support SSH protocol version 1 do this so that they can choose a protocol version based on the server's identification string. When PROXY protocol v2 is enabled on an NLB target group, the NLB doesn't deliver the server's identification string to the client until the client sends data. These clients connect and wait for the server's identification string, so they never send their own, and the connection stalls until it times out. + +The following table lists common SSH clients and the minimum version of each that is known to be compatible with PROXY protocol v2 in its default configuration. This list isn't comprehensive. An older version might also work if you configure it to use only SSH protocol version 2. If you use a client that isn't in this table, test its compatibility before you enable PROXY protocol v2. @@ -43,3 +44,0 @@ Client | Minimum version -JSch | 0.1.28 -OpenSSH | 6.2 -Apache MINA SSHD | 2.3.0 @@ -47,6 +46,10 @@ WinSCP | 5.8.1 -Rebex SSH | 2.0.4086 -libssh2 | 1.2.2 -Paramiko | 1.15.1 -Maverick Legacy | 1.7.15 -ssh2 (Node.js) | 0.0.23 -SSHJ | 0.19.1 +OpenSSH | 6.2 +JSch | 0.1.34 +Paramiko | All versions +SSH.NET | 2020.0.0 +FileZilla | 3.14.0 +ssh2 (Node.js) | All versions +Apache MINA SSHD | All versions +libssh2 | 0.6 +SSHJ | All versions +Cyberduck | 2.2