Differences between current version and previous revision of ssh(1).
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 7 | Last edited on Saturday, December 25, 2004 6:59:43 pm | by AristotlePagaltzis | |
| Older page: | version 6 | Last edited on Friday, December 10, 2004 12:14:09 am | by GustavoZaera | Revert |
@@ -38,10 +38,8 @@
When the user's identity has been accepted by the server, the server either executes the given command, or logs into the machine and gives the user a normal shell on the remote machine. All communication with the remote command or shell will be automatically encrypted.
If a pseudo-terminal has been allocated (normal login session), the user may use the escape characters noted below.
If no pseudo tty 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.
The session terminates when the command or shell on the remote machine exits and all X11 and TCP/IP connections have been closed. The exit status of the remote program is returned as the exit status of ssh.
-
-For shell scripts that execute a remote command with SSH, redirecting the STDERR on the remote machine to /dev/null is often desired to avoid displaying the remote machines's SSH banner. This is done by ssh [options] remote_machine 2>/dev/null.
__Escape Characters__
When a pseudo terminal has been requested, ssh supports a number of functions through the use of an escape character.
