new string: ssh escape sequence

[minimaxir]

new string: ssh escape sequence

[killerbees19]

Maybe that was an issue in year 2017, but currently it's not the case? (Tested at Ubuntu 20.04)

$ echo -e '\n~.' | ssh example.net -- 'dd of=/tmp/test.txt'
0+1 records in
0+1 records out
4 bytes (4 B) copied, 0.000616387 s, 6.5 kB/s

Quote from man page:

If an interactive session is requested ssh by default will only request a pseudo-terminal (pty) for interactive sessions when the client has one. The flags -T and -t can be used to override this behaviour.

If a pseudo-terminal has been allocated the user may use the escape characters noted below.

If no pseudo-terminal has been allocated, the session is transparent and can be used to reliably transfer binary data. On most systems, setting the escape character to “none” will also make the session transparent even if a tty is used.

If you call ssh with command argument, it's not an interactive session. Therefore no pseudo-terminal will be allocated.

If you pipe something into ssh without command argument, it'll display a warning and skip pseudo-terminal allocation:

$ echo | ssh example.net
Pseudo-terminal will not be allocated because stdin is not a terminal.

[…]

So this should be safe at the moment: tar c . | ssh example.net -- 'tar x'

Anyways, it's still a nice idea to add it to the list. 😁 👍