3 .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
4 .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
5 .\" All rights reserved
7 .\" As far as I am concerned, the code I have written for this software
8 .\" can be used freely for any purpose. Any derived versions of this
9 .\" software must be clearly marked as such, and if the derived work is
10 .\" incompatible with the protocol description in the RFC file, it must be
11 .\" called by a name other than "ssh" or "Secure Shell".
13 .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
14 .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
15 .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
17 .\" Redistribution and use in source and binary forms, with or without
18 .\" modification, are permitted provided that the following conditions
20 .\" 1. Redistributions of source code must retain the above copyright
21 .\" notice, this list of conditions and the following disclaimer.
22 .\" 2. Redistributions in binary form must reproduce the above copyright
23 .\" notice, this list of conditions and the following disclaimer in the
24 .\" documentation and/or other materials provided with the distribution.
26 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
27 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
28 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
29 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
30 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
31 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
32 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
33 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
34 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
35 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
37 .\" $OpenBSD: ssh.1,v 1.277 2008/07/02 13:47:39 djm Exp $
44 .Nd OpenSSH SSH client (remote login program)
47 .Op Fl 1246AaCfgKkMNnqsTtVvXxY
48 .Op Fl b Ar bind_address
49 .Op Fl c Ar cipher_spec
52 .Oo Ar bind_address : Oc
56 .Op Fl e Ar escape_char
57 .Op Fl F Ar configfile
59 .Op Fl i Ar identity_file
63 .Oo Ar bind_address : Oc
64 .Ar port : host : hostport
68 .Op Fl l Ar login_name
76 .Oo Ar bind_address : Oc
77 .Ar port : host : hostport
82 .Oo Fl w Ar local_tun Ns
83 .Op : Ns Ar remote_tun Oc
84 .Oo Ar user Ns @ Oc Ns Ar hostname
89 (SSH client) is a program for logging into a remote machine and for
90 executing commands on a remote machine.
91 It is intended to replace rlogin and rsh,
92 and provide secure encrypted communications between
93 two untrusted hosts over an insecure network.
94 X11 connections and arbitrary TCP ports
95 can also be forwarded over the secure channel.
98 connects and logs into the specified
104 his/her identity to the remote machine using one of several methods
105 depending on the protocol version used (see below).
110 it is executed on the remote host instead of a login shell.
112 The options are as follows:
117 to try protocol version 1 only.
121 to try protocol version 2 only.
125 to use IPv4 addresses only.
129 to use IPv6 addresses only.
131 Enables forwarding of the authentication agent connection.
132 This can also be specified on a per-host basis in a configuration file.
134 Agent forwarding should be enabled with caution.
135 Users with the ability to bypass file permissions on the remote host
136 (for the agent's Unix-domain socket)
137 can access the local agent through the forwarded connection.
138 An attacker cannot obtain key material from the agent,
139 however they can perform operations on the keys that enable them to
140 authenticate using the identities loaded into the agent.
142 Disables forwarding of the authentication agent connection.
143 .It Fl b Ar bind_address
146 on the local machine as the source address
148 Only useful on systems with more than one address.
150 Requests compression of all data (including stdin, stdout, stderr, and
151 data for forwarded X11 and TCP connections).
152 The compression algorithm is the same used by
156 can be controlled by the
158 option for protocol version 1.
159 Compression is desirable on modem lines and other
160 slow connections, but will only slow down things on fast networks.
161 The default value can be set on a host-by-host basis in the
162 configuration files; see the
165 .It Fl c Ar cipher_spec
166 Selects the cipher specification for encrypting the session.
168 Protocol version 1 allows specification of a single cipher.
169 The supported values are
175 (triple-des) is an encrypt-decrypt-encrypt triple with three different keys.
176 It is believed to be secure.
178 is a fast block cipher; it appears very secure and is much faster than
181 is only supported in the
183 client for interoperability with legacy protocol 1 implementations
184 that do not support the
187 Its use is strongly discouraged due to cryptographic weaknesses.
191 For protocol version 2,
193 is a comma-separated list of ciphers
194 listed in order of preference.
195 The supported ciphers are:
210 .Bd -literal -offset indent
211 aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,
212 arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
213 aes192-ctr,aes256-ctr
217 .Oo Ar bind_address : Oc
223 application-level port forwarding.
224 This works by allocating a socket to listen to
226 on the local side, optionally bound to the specified
228 Whenever a connection is made to this port, the
229 connection is forwarded over the secure channel, and the application
230 protocol is then used to determine where to connect to from the
232 Currently the SOCKS4 and SOCKS5 protocols are supported, and
234 will act as a SOCKS server.
235 Only root can forward privileged ports.
236 Dynamic port forwardings can also be specified in the configuration file.
238 IPv6 addresses can be specified with an alternative syntax:
241 .Op Ar bind_address No /
245 or by enclosing the address in square brackets.
246 Only the superuser can forward privileged ports.
247 By default, the local port is bound in accordance with the
252 may be used to bind the connection to a specific address.
257 indicates that the listening port be bound for local use only, while an
260 indicates that the port should be available from all interfaces.
261 .It Fl e Ar escape_char
262 Sets the escape character for sessions with a pty (default:
264 The escape character is only recognized at the beginning of a line.
265 The escape character followed by a dot
267 closes the connection;
268 followed by control-Z suspends the connection;
269 and followed by itself sends the escape character once.
270 Setting the character to
272 disables any escapes and makes the session fully transparent.
273 .It Fl F Ar configfile
274 Specifies an alternative per-user configuration file.
275 If a configuration file is given on the command line,
276 the system-wide configuration file
277 .Pq Pa /etc/ssh/ssh_config
279 The default for the per-user configuration file is
284 to go to background just before command execution.
287 is going to ask for passwords or passphrases, but the user
288 wants it in the background.
291 The recommended way to start X11 programs at a remote site is with
293 .Ic ssh -f host xterm .
296 .Cm ExitOnForwardFailure
297 configuration option is set to
299 then a client started with
301 will wait for all remote port forwards to be successfully established
302 before placing itself in the background.
304 Allows remote hosts to connect to local forwarded ports.
305 .It Fl I Ar smartcard_device
308 should use to communicate with a smartcard used for storing the user's
310 This option is only available if support for smartcard devices
311 is compiled in (default is no support).
312 .It Fl i Ar identity_file
313 Selects a file from which the identity (private key) for
314 RSA or DSA authentication is read.
317 for protocol version 1, and
321 for protocol version 2.
322 Identity files may also be specified on
323 a per-host basis in the configuration file.
324 It is possible to have multiple
326 options (and multiple identities specified in
327 configuration files).
329 Enables GSSAPI-based authentication and forwarding (delegation) of GSSAPI
330 credentials to the server.
332 Disables forwarding (delegation) of GSSAPI credentials to the server.
335 .Oo Ar bind_address : Oc
336 .Ar port : host : hostport
339 Specifies that the given port on the local (client) host is to be
340 forwarded to the given host and port on the remote side.
341 This works by allocating a socket to listen to
343 on the local side, optionally bound to the specified
345 Whenever a connection is made to this port, the
346 connection is forwarded over the secure channel, and a connection is
351 from the remote machine.
352 Port forwardings can also be specified in the configuration file.
353 IPv6 addresses can be specified with an alternative syntax:
356 .Op Ar bind_address No /
357 .Ar port No / Ar host No /
361 or by enclosing the address in square brackets.
362 Only the superuser can forward privileged ports.
363 By default, the local port is bound in accordance with the
368 may be used to bind the connection to a specific address.
373 indicates that the listening port be bound for local use only, while an
376 indicates that the port should be available from all interfaces.
377 .It Fl l Ar login_name
378 Specifies the user to log in as on the remote machine.
379 This also may be specified on a per-host basis in the configuration file.
385 mode for connection sharing.
392 mode with confirmation required before slave connections are accepted.
393 Refer to the description of
399 Additionally, for protocol version 2 a comma-separated list of MAC
400 (message authentication code) algorithms can
401 be specified in order of preference.
404 keyword for more information.
406 Do not execute a remote command.
407 This is useful for just forwarding ports
408 (protocol version 2 only).
412 (actually, prevents reading from stdin).
413 This must be used when
415 is run in the background.
416 A common trick is to use this to run X11 programs on a remote machine.
418 .Ic ssh -n shadows.cs.hut.fi emacs &
419 will start an emacs on shadows.cs.hut.fi, and the X11
420 connection will be automatically forwarded over an encrypted channel.
423 program will be put in the background.
424 (This does not work if
426 needs to ask for a password or passphrase; see also the
430 Control an active connection multiplexing master process.
433 option is specified, the
435 argument is interpreted and passed to the master process.
438 (check that the master process is running) and
440 (request the master to exit).
442 Can be used to give options in the format used in the configuration file.
443 This is useful for specifying options for which there is no separate
445 For full details of the options listed below, and their possible values, see
448 .Bl -tag -width Ds -offset indent -compact
452 .It ChallengeResponseAuthentication
456 .It ClearAllForwardings
459 .It ConnectionAttempts
465 .It ExitOnForwardFailure
468 .It ForwardX11Trusted
470 .It GlobalKnownHostsFile
471 .It GSSAPIAuthentication
472 .It GSSAPIDelegateCredentials
475 .It HostbasedAuthentication
476 .It HostKeyAlgorithms
481 .It KbdInteractiveDevices
486 .It NoHostAuthenticationForLocalhost
487 .It NumberOfPasswordPrompts
488 .It PasswordAuthentication
489 .It PermitLocalCommand
491 .It PreferredAuthentications
494 .It PubkeyAuthentication
497 .It RhostsRSAAuthentication
498 .It RSAAuthentication
500 .It ServerAliveInterval
501 .It ServerAliveCountMax
503 .It StrictHostKeyChecking
507 .It UsePrivilegedPort
509 .It UserKnownHostsFile
516 Port to connect to on the remote host.
517 This can be specified on a
518 per-host basis in the configuration file.
521 Causes most warning and diagnostic messages to be suppressed.
524 .Oo Ar bind_address : Oc
525 .Ar port : host : hostport
528 Specifies that the given port on the remote (server) host is to be
529 forwarded to the given host and port on the local side.
530 This works by allocating a socket to listen to
532 on the remote side, and whenever a connection is made to this port, the
533 connection is forwarded over the secure channel, and a connection is
538 from the local machine.
540 Port forwardings can also be specified in the configuration file.
541 Privileged ports can be forwarded only when
542 logging in as root on the remote machine.
543 IPv6 addresses can be specified by enclosing the address in square braces or
544 using an alternative syntax:
547 .Op Ar bind_address No /
548 .Ar host No / Ar port No /
553 By default, the listening socket on the server will be bound to the loopback
555 This may be overriden by specifying a
561 indicates that the remote socket should listen on all interfaces.
564 will only succeed if the server's
566 option is enabled (see
567 .Xr sshd_config 5 ) .
569 Specifies the location of a control socket for connection sharing.
570 Refer to the description of
578 May be used to request invocation of a subsystem on the remote system.
579 Subsystems are a feature of the SSH2 protocol which facilitate the use
580 of SSH as a secure transport for other applications (eg.\&
582 The subsystem is specified as the remote command.
584 Disable pseudo-tty allocation.
586 Force pseudo-tty allocation.
587 This can be used to execute arbitrary
588 screen-based programs on a remote machine, which can be very useful,
589 e.g. when implementing menu services.
592 options force tty allocation, even if
596 Display the version number and exit.
601 to print debugging messages about its progress.
603 debugging connection, authentication, and configuration problems.
606 options increase the verbosity.
609 .Ar local_tun Ns Op : Ns Ar remote_tun
613 device forwarding with the specified
615 devices between the client
620 The devices may be specified by numerical ID or the keyword
622 which uses the next available tunnel device.
625 is not specified, it defaults to
635 directive is unset, it is set to the default tunnel mode, which is
638 Enables X11 forwarding.
639 This can also be specified on a per-host basis in a configuration file.
641 X11 forwarding should be enabled with caution.
642 Users with the ability to bypass file permissions on the remote host
643 (for the user's X authorization database)
644 can access the local X11 display through the forwarded connection.
645 An attacker may then be able to perform activities such as keystroke monitoring.
647 For this reason, X11 forwarding is subjected to X11 SECURITY extension
648 restrictions by default.
653 .Cm ForwardX11Trusted
656 for more information.
658 Disables X11 forwarding.
660 Enables trusted X11 forwarding.
661 Trusted X11 forwardings are not subjected to the X11 SECURITY extension
666 may additionally obtain configuration data from
667 a per-user configuration file and a system-wide configuration file.
668 The file format and configuration options are described in
672 exits with the exit status of the remote command or with 255
673 if an error occurred.
675 The OpenSSH SSH client supports SSH protocols 1 and 2.
676 Protocol 2 is the default, with
678 falling back to protocol 1 if it detects protocol 2 is unsupported.
679 These settings may be altered using the
683 or enforced using the
688 Both protocols support similar authentication methods,
689 but protocol 2 is preferred since
690 it provides additional mechanisms for confidentiality
691 (the traffic is encrypted using AES, 3DES, Blowfish, CAST128, or Arcfour)
692 and integrity (hmac-md5, hmac-sha1, umac-64, hmac-ripemd160).
693 Protocol 1 lacks a strong mechanism for ensuring the
694 integrity of the connection.
696 The methods available for authentication are:
697 GSSAPI-based authentication,
698 host-based authentication,
699 public key authentication,
700 challenge-response authentication,
701 and password authentication.
702 Authentication methods are tried in the order specified above,
703 though protocol 2 has a configuration option to change the default order:
704 .Cm PreferredAuthentications .
706 Host-based authentication works as follows:
707 If the machine the user logs in from is listed in
710 .Pa /etc/shosts.equiv
711 on the remote machine, and the user names are
712 the same on both sides, or if the files
716 exist in the user's home directory on the
717 remote machine and contain a line containing the name of the client
718 machine and the name of the user on that machine, the user is
719 considered for login.
720 Additionally, the server
722 be able to verify the client's
723 host key (see the description of
724 .Pa /etc/ssh/ssh_known_hosts
726 .Pa ~/.ssh/known_hosts ,
728 for login to be permitted.
729 This authentication method closes security holes due to IP
730 spoofing, DNS spoofing, and routing spoofing.
731 [Note to the administrator:
732 .Pa /etc/hosts.equiv ,
734 and the rlogin/rsh protocol in general, are inherently insecure and should be
735 disabled if security is desired.]
737 Public key authentication works as follows:
738 The scheme is based on public-key cryptography,
740 where encryption and decryption are done using separate keys,
741 and it is unfeasible to derive the decryption key from the encryption key.
742 The idea is that each user creates a public/private
743 key pair for authentication purposes.
744 The server knows the public key, and only the user knows the private key.
746 implements public key authentication protocol automatically,
747 using either the RSA or DSA algorithms.
748 Protocol 1 is restricted to using only RSA keys,
749 but protocol 2 may use either.
754 contains a brief discussion of the two algorithms.
757 .Pa ~/.ssh/authorized_keys
758 lists the public keys that are permitted for logging in.
759 When the user logs in, the
761 program tells the server which key pair it would like to use for
763 The client proves that it has access to the private key
764 and the server checks that the corresponding public key
765 is authorized to accept the account.
767 The user creates his/her key pair by running
769 This stores the private key in
777 and stores the public key in
778 .Pa ~/.ssh/identity.pub
780 .Pa ~/.ssh/id_dsa.pub
783 .Pa ~/.ssh/id_rsa.pub
785 in the user's home directory.
786 The user should then copy the public key
788 .Pa ~/.ssh/authorized_keys
789 in his/her home directory on the remote machine.
792 file corresponds to the conventional
794 file, and has one key
795 per line, though the lines can be very long.
796 After this, the user can log in without giving the password.
798 The most convenient way to use public key authentication may be with an
799 authentication agent.
802 for more information.
804 Challenge-response authentication works as follows:
805 The server sends an arbitrary
807 text, and prompts for a response.
808 Protocol 2 allows multiple challenges and responses;
809 protocol 1 is restricted to just one challenge/response.
810 Examples of challenge-response authentication include
811 BSD Authentication (see
813 and PAM (some non-OpenBSD systems).
815 Finally, if other authentication methods fail,
817 prompts the user for a password.
818 The password is sent to the remote
819 host for checking; however, since all communications are encrypted,
820 the password cannot be seen by someone listening on the network.
823 automatically maintains and checks a database containing
824 identification for all hosts it has ever been used with.
825 Host keys are stored in
826 .Pa ~/.ssh/known_hosts
827 in the user's home directory.
828 Additionally, the file
829 .Pa /etc/ssh/ssh_known_hosts
830 is automatically checked for known hosts.
831 Any new hosts are automatically added to the user's file.
832 If a host's identification ever changes,
834 warns about this and disables password authentication to prevent
835 server spoofing or man-in-the-middle attacks,
836 which could otherwise be used to circumvent the encryption.
838 .Cm StrictHostKeyChecking
839 option can be used to control logins to machines whose
840 host key is not known or has changed.
842 When the user's identity has been accepted by the server, the server
843 either executes the given command, or logs into the machine and gives
844 the user a normal shell on the remote machine.
845 All communication with
846 the remote command or shell will be automatically encrypted.
848 If a pseudo-terminal has been allocated (normal login session), the
849 user may use the escape characters noted below.
851 If no pseudo-tty has been allocated,
852 the session is transparent and can be used to reliably transfer binary data.
853 On most systems, setting the escape character to
855 will also make the session transparent even if a tty is used.
857 The session terminates when the command or shell on the remote
858 machine exits and all X11 and TCP connections have been closed.
859 .Sh ESCAPE CHARACTERS
860 When a pseudo-terminal has been requested,
862 supports a number of functions through the use of an escape character.
864 A single tilde character can be sent as
866 or by following the tilde by a character other than those described below.
867 The escape character must always follow a newline to be interpreted as
869 The escape character can be changed in configuration files using the
871 configuration directive or on the command line by the
875 The supported escapes (assuming the default
885 List forwarded connections.
889 at logout when waiting for forwarded connection / X11 sessions to terminate.
891 Display a list of escape characters.
893 Send a BREAK to the remote system
894 (only useful for SSH protocol version 2 and if the peer supports it).
897 Currently this allows the addition of port forwardings using the
902 It also allows the cancellation of existing remote port-forwardings
905 .Fl KR Oo Ar bind_address : Oc Ar port .
907 .Ic !\& Ns Ar command
908 allows the user to execute a local command if the
909 .Ic PermitLocalCommand
912 Basic help is available, using the
916 Request rekeying of the connection
917 (only useful for SSH protocol version 2 and if the peer supports it).
920 Forwarding of arbitrary TCP connections over the secure channel can
921 be specified either on the command line or in a configuration file.
922 One possible application of TCP forwarding is a secure connection to a
923 mail server; another is going through firewalls.
925 In the example below, we look at encrypting communication between
926 an IRC client and server, even though the IRC server does not directly
927 support encrypted communications.
928 This works as follows:
929 the user connects to the remote host using
931 specifying a port to be used to forward connections
932 to the remote server.
933 After that it is possible to start the service which is to be encrypted
934 on the client machine,
935 connecting to the same local port,
938 will encrypt and forward the connection.
940 The following example tunnels an IRC session from client machine
944 .Dq server.example.com :
945 .Bd -literal -offset 4n
946 $ ssh -f -L 1234:localhost:6667 server.example.com sleep 10
947 $ irc -c '#users' -p 1234 pinky 127.0.0.1
950 This tunnels a connection to IRC server
951 .Dq server.example.com ,
957 It doesn't matter which port is used,
958 as long as it's greater than 1023
959 (remember, only root can open sockets on privileged ports)
960 and doesn't conflict with any ports already in use.
961 The connection is forwarded to port 6667 on the remote server,
962 since that's the standard port for IRC services.
968 and the remote command
970 is specified to allow an amount of time
971 (10 seconds, in the example)
972 to start the service which is to be tunnelled.
973 If no connections are made within the time specified,
981 (or see the description of the
987 and the user is using X11 (the
989 environment variable is set), the connection to the X11 display is
990 automatically forwarded to the remote side in such a way that any X11
991 programs started from the shell (or command) will go through the
992 encrypted channel, and the connection to the real X server will be made
993 from the local machine.
994 The user should not manually set
996 Forwarding of X11 connections can be
997 configured on the command line or in configuration files.
1003 will point to the server machine, but with a display number greater than zero.
1004 This is normal, and happens because
1008 X server on the server machine for forwarding the
1009 connections over the encrypted channel.
1012 will also automatically set up Xauthority data on the server machine.
1013 For this purpose, it will generate a random authorization cookie,
1014 store it in Xauthority on the server, and verify that any forwarded
1015 connections carry this cookie and replace it by the real cookie when
1016 the connection is opened.
1017 The real authentication cookie is never
1018 sent to the server machine (and no cookies are sent in the plain).
1024 (or see the description of the
1029 the user is using an authentication agent, the connection to the agent
1030 is automatically forwarded to the remote side.
1031 .Sh VERIFYING HOST KEYS
1032 When connecting to a server for the first time,
1033 a fingerprint of the server's public key is presented to the user
1035 .Cm StrictHostKeyChecking
1037 Fingerprints can be determined using
1040 .Dl $ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key
1042 If the fingerprint is already known, it can be matched
1043 and the key can be accepted or rejected.
1044 Because of the difficulty of comparing host keys
1045 just by looking at hex strings,
1046 there is also support to compare host keys visually,
1053 a small ASCII graphic gets displayed on every login to a server, no matter
1054 if the session itself is interactive or not.
1055 By learning the pattern a known server produces, a user can easily
1056 find out that the host key has changed when a completely different pattern
1058 Because these patterns are not unambiguous however, a pattern that looks
1059 similar to the pattern remembered only gives a good probability that the
1060 host key is the same, not guaranteed proof.
1062 To get a listing of the fingerprints along with their random art for
1063 all known hosts, the following command line can be used:
1065 .Dl $ ssh-keygen -lv -f ~/.ssh/known_hosts
1067 If the fingerprint is unknown,
1068 an alternative method of verification is available:
1069 SSH fingerprints verified by DNS.
1070 An additional resource record (RR),
1072 is added to a zonefile
1073 and the connecting client is able to match the fingerprint
1074 with that of the key presented.
1076 In this example, we are connecting a client to a server,
1077 .Dq host.example.com .
1078 The SSHFP resource records should first be added to the zonefile for
1080 .Bd -literal -offset indent
1081 $ ssh-keygen -r host.example.com.
1084 The output lines will have to be added to the zonefile.
1085 To check that the zone is answering fingerprint queries:
1087 .Dl $ dig -t SSHFP host.example.com
1089 Finally the client connects:
1090 .Bd -literal -offset indent
1091 $ ssh -o "VerifyHostKeyDNS ask" host.example.com
1093 Matching host key fingerprint found in DNS.
1094 Are you sure you want to continue connecting (yes/no)?
1098 .Cm VerifyHostKeyDNS
1101 for more information.
1102 .Sh SSH-BASED VIRTUAL PRIVATE NETWORKS
1104 contains support for Virtual Private Network (VPN) tunnelling
1107 network pseudo-device,
1108 allowing two networks to be joined securely.
1111 configuration option
1113 controls whether the server supports this,
1114 and at what level (layer 2 or 3 traffic).
1116 The following example would connect client network 10.0.50.0/24
1117 with remote network 10.0.99.0/24 using a point-to-point connection
1118 from 10.1.1.1 to 10.1.1.2,
1119 provided that the SSH server running on the gateway to the remote network,
1120 at 192.168.1.15, allows it.
1123 .Bd -literal -offset indent
1124 # ssh -f -w 0:1 192.168.1.15 true
1125 # ifconfig tun0 10.1.1.1 10.1.1.2 netmask 255.255.255.252
1126 # route add 10.0.99.0/24 10.1.1.2
1130 .Bd -literal -offset indent
1131 # ifconfig tun1 10.1.1.2 10.1.1.1 netmask 255.255.255.252
1132 # route add 10.0.50.0/24 10.1.1.1
1135 Client access may be more finely tuned via the
1136 .Pa /root/.ssh/authorized_keys
1137 file (see below) and the
1140 The following entry would permit connections on
1144 and on tun device 2 from user
1149 .Dq forced-commands-only :
1150 .Bd -literal -offset 2n
1151 tunnel="1",command="sh /etc/netstart tun1" ssh-rsa ... jane
1152 tunnel="2",command="sh /etc/netstart tun2" ssh-rsa ... john
1155 Since an SSH-based setup entails a fair amount of overhead,
1156 it may be more suited to temporary setups,
1157 such as for wireless VPNs.
1158 More permanent VPNs are better provided by tools such as
1164 will normally set the following environment variables:
1165 .Bl -tag -width "SSH_ORIGINAL_COMMAND"
1169 variable indicates the location of the X11 server.
1170 It is automatically set by
1172 to point to a value of the form
1176 indicates the host where the shell runs, and
1178 is an integer \*(Ge 1.
1180 uses this special value to forward X11 connections over the secure
1182 The user should normally not set
1185 will render the X11 connection insecure (and will require the user to
1186 manually copy any required authorization cookies).
1188 Set to the path of the user's home directory.
1192 set for compatibility with systems that use this variable.
1194 Set to the path of the user's mailbox.
1198 as specified when compiling
1203 needs a passphrase, it will read the passphrase from the current
1204 terminal if it was run from a terminal.
1207 does not have a terminal associated with it but
1211 are set, it will execute the program specified by
1213 and open an X11 window to read the passphrase.
1214 This is particularly useful when calling
1219 (Note that on some machines it
1220 may be necessary to redirect the input from
1223 .It Ev SSH_AUTH_SOCK
1224 Identifies the path of a
1226 socket used to communicate with the agent.
1227 .It Ev SSH_CONNECTION
1228 Identifies the client and server ends of the connection.
1229 The variable contains
1230 four space-separated values: client IP address, client port number,
1231 server IP address, and server port number.
1232 .It Ev SSH_ORIGINAL_COMMAND
1233 This variable contains the original command line if a forced command
1235 It can be used to extract the original arguments.
1237 This is set to the name of the tty (path to the device) associated
1238 with the current shell or command.
1239 If the current session has no tty,
1240 this variable is not set.
1242 This variable is set to indicate the present time zone if it
1243 was set when the daemon was started (i.e. the daemon passes the value
1244 on to new connections).
1246 Set to the name of the user logging in.
1252 .Pa ~/.ssh/environment ,
1253 and adds lines of the format
1255 to the environment if the file exists and users are allowed to
1256 change their environment.
1257 For more information, see the
1258 .Cm PermitUserEnvironment
1262 .Bl -tag -width Ds -compact
1264 This file is used for host-based authentication (see above).
1265 On some machines this file may need to be
1266 world-readable if the user's home directory is on an NFS partition,
1270 Additionally, this file must be owned by the user,
1271 and must not have write permissions for anyone else.
1273 permission for most machines is read/write for the user, and not
1274 accessible by others.
1277 This file is used in exactly the same way as
1279 but allows host-based authentication without permitting login with
1283 This directory is the default location for all user-specific configuration
1284 and authentication information.
1285 There is no general requirement to keep the entire contents of this directory
1286 secret, but the recommended permissions are read/write/execute for the user,
1287 and not accessible by others.
1289 .It ~/.ssh/authorized_keys
1290 Lists the public keys (RSA/DSA) that can be used for logging in as this user.
1291 The format of this file is described in the
1294 This file is not highly sensitive, but the recommended
1295 permissions are read/write for the user, and not accessible by others.
1298 This is the per-user configuration file.
1299 The file format and configuration options are described in
1301 Because of the potential for abuse, this file must have strict permissions:
1302 read/write for the user, and not accessible by others.
1304 .It ~/.ssh/environment
1305 Contains additional definitions for environment variables; see
1312 Contains the private key for authentication.
1314 contain sensitive data and should be readable by the user but not
1315 accessible by others (read/write/execute).
1317 will simply ignore a private key file if it is accessible by others.
1318 It is possible to specify a passphrase when
1319 generating the key which will be used to encrypt the
1320 sensitive part of this file using 3DES.
1322 .It ~/.ssh/identity.pub
1323 .It ~/.ssh/id_dsa.pub
1324 .It ~/.ssh/id_rsa.pub
1325 Contains the public key for authentication.
1327 sensitive and can (but need not) be readable by anyone.
1329 .It ~/.ssh/known_hosts
1330 Contains a list of host keys for all hosts the user has logged into
1331 that are not already in the systemwide list of known host keys.
1334 for further details of the format of this file.
1337 Commands in this file are executed by
1339 when the user logs in, just before the user's shell (or command) is
1343 manual page for more information.
1345 .It /etc/hosts.equiv
1346 This file is for host-based authentication (see above).
1347 It should only be writable by root.
1349 .It /etc/shosts.equiv
1350 This file is used in exactly the same way as
1352 but allows host-based authentication without permitting login with
1355 .It Pa /etc/ssh/ssh_config
1356 Systemwide configuration file.
1357 The file format and configuration options are described in
1360 .It /etc/ssh/ssh_host_key
1361 .It /etc/ssh/ssh_host_dsa_key
1362 .It /etc/ssh/ssh_host_rsa_key
1363 These three files contain the private parts of the host keys
1364 and are used for host-based authentication.
1365 If protocol version 1 is used,
1367 must be setuid root, since the host key is readable only by root.
1368 For protocol version 2,
1372 to access the host keys,
1373 eliminating the requirement that
1375 be setuid root when host-based authentication is used.
1380 .It /etc/ssh/ssh_known_hosts
1381 Systemwide list of known host keys.
1382 This file should be prepared by the
1383 system administrator to contain the public host keys of all machines in the
1385 It should be world-readable.
1388 for further details of the format of this file.
1391 Commands in this file are executed by
1393 when the user logs in, just before the user's shell (or command) is started.
1396 manual page for more information.
1412 .%T "The Secure Shell (SSH) Protocol Assigned Numbers"
1417 .%T "The Secure Shell (SSH) Protocol Architecture"
1422 .%T "The Secure Shell (SSH) Authentication Protocol"
1427 .%T "The Secure Shell (SSH) Transport Layer Protocol"
1432 .%T "The Secure Shell (SSH) Connection Protocol"
1437 .%T "Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints"
1442 .%T "Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)"
1447 .%T "The Secure Shell (SSH) Session Channel Break Extension"
1452 .%T "The Secure Shell (SSH) Transport Layer Encryption Modes"
1457 .%T "Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol"
1462 .%T "Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol"
1467 .%T "The Secure Shell (SSH) Public Key File Format"
1471 .%T "Hash Visualization: a New Technique to improve Real-World Security"
1475 .%O "International Workshop on Cryptographic Techniques and E-Commerce (CrypTEC '99)"
1478 OpenSSH is a derivative of the original and free
1479 ssh 1.2.12 release by Tatu Ylonen.
1480 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1481 Theo de Raadt and Dug Song
1482 removed many bugs, re-added newer features and
1484 Markus Friedl contributed the support for SSH
1485 protocol versions 1.5 and 2.0.
projects / FreeBSD / releng / 7.2.git / blob