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.302 2010/03/05 10:28:21 djm Exp $
44 .Nd OpenSSH SSH client (remote login program)
47 .Op Fl 1246AaCfgKkMNnqsTtVvXxYy
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
60 .Op Fl i Ar identity_file
64 .Oo Ar bind_address : Oc
65 .Ar port : host : hostport
69 .Op Fl l Ar login_name
77 .Oo Ar bind_address : Oc
78 .Ar port : host : hostport
82 .Op Fl W Ar host : Ns Ar port
83 .Oo Fl w Ar local_tun Ns
84 .Op : Ns Ar remote_tun Oc
85 .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
138 socket) can access the local agent through the forwarded connection.
139 An attacker cannot obtain key material from the agent,
140 however they can perform operations on the keys that enable them to
141 authenticate using the identities loaded into the agent.
143 Disables forwarding of the authentication agent connection.
144 .It Fl b Ar bind_address
147 on the local machine as the source address
149 Only useful on systems with more than one address.
151 Requests compression of all data (including stdin, stdout, stderr, and
152 data for forwarded X11 and TCP connections).
153 The compression algorithm is the same used by
157 can be controlled by the
159 option for protocol version 1.
160 Compression is desirable on modem lines and other
161 slow connections, but will only slow down things on fast networks.
162 The default value can be set on a host-by-host basis in the
163 configuration files; see the
166 .It Fl c Ar cipher_spec
167 Selects the cipher specification for encrypting the session.
169 Protocol version 1 allows specification of a single cipher.
170 The supported values are
176 (triple-des) is an encrypt-decrypt-encrypt triple with three different keys.
177 It is believed to be secure.
179 is a fast block cipher; it appears very secure and is much faster than
182 is only supported in the
184 client for interoperability with legacy protocol 1 implementations
185 that do not support the
188 Its use is strongly discouraged due to cryptographic weaknesses.
192 For protocol version 2,
194 is a comma-separated list of ciphers
195 listed in order of preference.
198 keyword for more information.
201 .Oo Ar bind_address : Oc
207 application-level port forwarding.
208 This works by allocating a socket to listen to
210 on the local side, optionally bound to the specified
212 Whenever a connection is made to this port, the
213 connection is forwarded over the secure channel, and the application
214 protocol is then used to determine where to connect to from the
216 Currently the SOCKS4 and SOCKS5 protocols are supported, and
218 will act as a SOCKS server.
219 Only root can forward privileged ports.
220 Dynamic port forwardings can also be specified in the configuration file.
222 IPv6 addresses can be specified with an alternative syntax:
225 .Op Ar bind_address No /
229 or by enclosing the address in square brackets.
230 Only the superuser can forward privileged ports.
231 By default, the local port is bound in accordance with the
236 may be used to bind the connection to a specific address.
241 indicates that the listening port be bound for local use only, while an
244 indicates that the port should be available from all interfaces.
245 .It Fl e Ar escape_char
246 Sets the escape character for sessions with a pty (default:
248 The escape character is only recognized at the beginning of a line.
249 The escape character followed by a dot
251 closes the connection;
252 followed by control-Z suspends the connection;
253 and followed by itself sends the escape character once.
254 Setting the character to
256 disables any escapes and makes the session fully transparent.
257 .It Fl F Ar configfile
258 Specifies an alternative per-user configuration file.
259 If a configuration file is given on the command line,
260 the system-wide configuration file
261 .Pq Pa /etc/ssh/ssh_config
263 The default for the per-user configuration file is
268 to go to background just before command execution.
271 is going to ask for passwords or passphrases, but the user
272 wants it in the background.
275 The recommended way to start X11 programs at a remote site is with
277 .Ic ssh -f host xterm .
280 .Cm ExitOnForwardFailure
281 configuration option is set to
283 then a client started with
285 will wait for all remote port forwards to be successfully established
286 before placing itself in the background.
288 Allows remote hosts to connect to local forwarded ports.
290 Specify the PKCS#11 shared library
292 should use to communicate with a PKCS#11 token providing the user's
294 .It Fl i Ar identity_file
295 Selects a file from which the identity (private key) for
296 RSA or DSA authentication is read.
299 for protocol version 1, and
303 for protocol version 2.
304 Identity files may also be specified on
305 a per-host basis in the configuration file.
306 It is possible to have multiple
308 options (and multiple identities specified in
309 configuration files).
311 will also try to load certificate information from the filename obtained
314 to identity filenames.
316 Enables GSSAPI-based authentication and forwarding (delegation) of GSSAPI
317 credentials to the server.
319 Disables forwarding (delegation) of GSSAPI credentials to the server.
322 .Oo Ar bind_address : Oc
323 .Ar port : host : hostport
326 Specifies that the given port on the local (client) host is to be
327 forwarded to the given host and port on the remote side.
328 This works by allocating a socket to listen to
330 on the local side, optionally bound to the specified
332 Whenever a connection is made to this port, the
333 connection is forwarded over the secure channel, and a connection is
338 from the remote machine.
339 Port forwardings can also be specified in the configuration file.
340 IPv6 addresses can be specified with an alternative syntax:
343 .Op Ar bind_address No /
344 .Ar port No / Ar host No /
348 or by enclosing the address in square brackets.
349 Only the superuser can forward privileged ports.
350 By default, the local port is bound in accordance with the
355 may be used to bind the connection to a specific address.
360 indicates that the listening port be bound for local use only, while an
363 indicates that the port should be available from all interfaces.
364 .It Fl l Ar login_name
365 Specifies the user to log in as on the remote machine.
366 This also may be specified on a per-host basis in the configuration file.
372 mode for connection sharing.
379 mode with confirmation required before slave connections are accepted.
380 Refer to the description of
386 Additionally, for protocol version 2 a comma-separated list of MAC
387 (message authentication code) algorithms can
388 be specified in order of preference.
391 keyword for more information.
393 Do not execute a remote command.
394 This is useful for just forwarding ports
395 (protocol version 2 only).
399 (actually, prevents reading from stdin).
400 This must be used when
402 is run in the background.
403 A common trick is to use this to run X11 programs on a remote machine.
405 .Ic ssh -n shadows.cs.hut.fi emacs &
406 will start an emacs on shadows.cs.hut.fi, and the X11
407 connection will be automatically forwarded over an encrypted channel.
410 program will be put in the background.
411 (This does not work if
413 needs to ask for a password or passphrase; see also the
417 Control an active connection multiplexing master process.
420 option is specified, the
422 argument is interpreted and passed to the master process.
425 (check that the master process is running) and
427 (request the master to exit).
429 Can be used to give options in the format used in the configuration file.
430 This is useful for specifying options for which there is no separate
432 For full details of the options listed below, and their possible values, see
435 .Bl -tag -width Ds -offset indent -compact
439 .It ChallengeResponseAuthentication
443 .It ClearAllForwardings
446 .It ConnectionAttempts
452 .It ExitOnForwardFailure
455 .It ForwardX11Trusted
457 .It GlobalKnownHostsFile
458 .It GSSAPIAuthentication
459 .It GSSAPIDelegateCredentials
462 .It HostbasedAuthentication
463 .It HostKeyAlgorithms
468 .It KbdInteractiveDevices
473 .It NoHostAuthenticationForLocalhost
474 .It NumberOfPasswordPrompts
475 .It PasswordAuthentication
476 .It PermitLocalCommand
479 .It PreferredAuthentications
482 .It PubkeyAuthentication
485 .It RhostsRSAAuthentication
486 .It RSAAuthentication
488 .It ServerAliveInterval
489 .It ServerAliveCountMax
490 .It StrictHostKeyChecking
494 .It UsePrivilegedPort
496 .It UserKnownHostsFile
503 Port to connect to on the remote host.
504 This can be specified on a
505 per-host basis in the configuration file.
508 Causes most warning and diagnostic messages to be suppressed.
511 .Oo Ar bind_address : Oc
512 .Ar port : host : hostport
515 Specifies that the given port on the remote (server) host is to be
516 forwarded to the given host and port on the local side.
517 This works by allocating a socket to listen to
519 on the remote side, and whenever a connection is made to this port, the
520 connection is forwarded over the secure channel, and a connection is
525 from the local machine.
527 Port forwardings can also be specified in the configuration file.
528 Privileged ports can be forwarded only when
529 logging in as root on the remote machine.
530 IPv6 addresses can be specified by enclosing the address in square braces or
531 using an alternative syntax:
534 .Op Ar bind_address No /
535 .Ar host No / Ar port No /
540 By default, the listening socket on the server will be bound to the loopback
542 This may be overridden by specifying a
548 indicates that the remote socket should listen on all interfaces.
551 will only succeed if the server's
553 option is enabled (see
554 .Xr sshd_config 5 ) .
560 the listen port will be dynamically allocated on the server and reported
561 to the client at run time.
563 Specifies the location of a control socket for connection sharing.
564 Refer to the description of
572 May be used to request invocation of a subsystem on the remote system.
573 Subsystems are a feature of the SSH2 protocol which facilitate the use
574 of SSH as a secure transport for other applications (eg.\&
576 The subsystem is specified as the remote command.
578 Disable pseudo-tty allocation.
580 Force pseudo-tty allocation.
581 This can be used to execute arbitrary
582 screen-based programs on a remote machine, which can be very useful,
583 e.g. when implementing menu services.
586 options force tty allocation, even if
590 Display the version number and exit.
595 to print debugging messages about its progress.
597 debugging connection, authentication, and configuration problems.
600 options increase the verbosity.
602 .It Fl W Ar host : Ns Ar port
603 Requests that standard input and output on the client be forwarded to
607 over the secure channel.
611 .Cm ExitOnForwardFailure
613 .Cm ClearAllForwardings
614 and works with Protocol version 2 only.
616 .Ar local_tun Ns Op : Ns Ar remote_tun
620 device forwarding with the specified
622 devices between the client
627 The devices may be specified by numerical ID or the keyword
629 which uses the next available tunnel device.
632 is not specified, it defaults to
642 directive is unset, it is set to the default tunnel mode, which is
645 Enables X11 forwarding.
646 This can also be specified on a per-host basis in a configuration file.
648 X11 forwarding should be enabled with caution.
649 Users with the ability to bypass file permissions on the remote host
650 (for the user's X authorization database)
651 can access the local X11 display through the forwarded connection.
652 An attacker may then be able to perform activities such as keystroke monitoring.
654 For this reason, X11 forwarding is subjected to X11 SECURITY extension
655 restrictions by default.
660 .Cm ForwardX11Trusted
663 for more information.
665 Disables X11 forwarding.
667 Enables trusted X11 forwarding.
668 Trusted X11 forwardings are not subjected to the X11 SECURITY extension
671 Send log information using the
674 By default this information is sent to stderr.
678 may additionally obtain configuration data from
679 a per-user configuration file and a system-wide configuration file.
680 The file format and configuration options are described in
684 exits with the exit status of the remote command or with 255
685 if an error occurred.
687 The OpenSSH SSH client supports SSH protocols 1 and 2.
688 The default is to use protocol 2 only,
689 though this can be changed via the
698 Both protocols support similar authentication methods,
699 but protocol 2 is the default since
700 it provides additional mechanisms for confidentiality
701 (the traffic is encrypted using AES, 3DES, Blowfish, CAST128, or Arcfour)
702 and integrity (hmac-md5, hmac-sha1, umac-64, hmac-ripemd160).
703 Protocol 1 lacks a strong mechanism for ensuring the
704 integrity of the connection.
706 The methods available for authentication are:
707 GSSAPI-based authentication,
708 host-based authentication,
709 public key authentication,
710 challenge-response authentication,
711 and password authentication.
712 Authentication methods are tried in the order specified above,
713 though protocol 2 has a configuration option to change the default order:
714 .Cm PreferredAuthentications .
716 Host-based authentication works as follows:
717 If the machine the user logs in from is listed in
720 .Pa /etc/shosts.equiv
721 on the remote machine, and the user names are
722 the same on both sides, or if the files
726 exist in the user's home directory on the
727 remote machine and contain a line containing the name of the client
728 machine and the name of the user on that machine, the user is
729 considered for login.
730 Additionally, the server
732 be able to verify the client's
733 host key (see the description of
734 .Pa /etc/ssh/ssh_known_hosts
736 .Pa ~/.ssh/known_hosts ,
738 for login to be permitted.
739 This authentication method closes security holes due to IP
740 spoofing, DNS spoofing, and routing spoofing.
741 [Note to the administrator:
742 .Pa /etc/hosts.equiv ,
744 and the rlogin/rsh protocol in general, are inherently insecure and should be
745 disabled if security is desired.]
747 Public key authentication works as follows:
748 The scheme is based on public-key cryptography,
750 where encryption and decryption are done using separate keys,
751 and it is unfeasible to derive the decryption key from the encryption key.
752 The idea is that each user creates a public/private
753 key pair for authentication purposes.
754 The server knows the public key, and only the user knows the private key.
756 implements public key authentication protocol automatically,
757 using either the RSA or DSA algorithms.
758 Protocol 1 is restricted to using only RSA keys,
759 but protocol 2 may use either.
764 contains a brief discussion of the two algorithms.
767 .Pa ~/.ssh/authorized_keys
768 lists the public keys that are permitted for logging in.
769 When the user logs in, the
771 program tells the server which key pair it would like to use for
773 The client proves that it has access to the private key
774 and the server checks that the corresponding public key
775 is authorized to accept the account.
777 The user creates his/her key pair by running
779 This stores the private key in
787 and stores the public key in
788 .Pa ~/.ssh/identity.pub
790 .Pa ~/.ssh/id_dsa.pub
793 .Pa ~/.ssh/id_rsa.pub
795 in the user's home directory.
796 The user should then copy the public key
798 .Pa ~/.ssh/authorized_keys
799 in his/her home directory on the remote machine.
802 file corresponds to the conventional
804 file, and has one key
805 per line, though the lines can be very long.
806 After this, the user can log in without giving the password.
808 A variation on public key authentication
809 is available in the form of certificate authentication:
810 instead of a set of public/private keys,
811 signed certificates are used.
812 This has the advantage that a single trusted certification authority
813 can be used in place of many public/private keys.
818 for more information.
820 The most convenient way to use public key or certificate authentication
821 may be with an authentication agent.
824 for more information.
826 Challenge-response authentication works as follows:
827 The server sends an arbitrary
829 text, and prompts for a response.
830 Protocol 2 allows multiple challenges and responses;
831 protocol 1 is restricted to just one challenge/response.
832 Examples of challenge-response authentication include
833 BSD Authentication (see
835 and PAM (some non-OpenBSD systems).
837 Finally, if other authentication methods fail,
839 prompts the user for a password.
840 The password is sent to the remote
841 host for checking; however, since all communications are encrypted,
842 the password cannot be seen by someone listening on the network.
845 automatically maintains and checks a database containing
846 identification for all hosts it has ever been used with.
847 Host keys are stored in
848 .Pa ~/.ssh/known_hosts
849 in the user's home directory.
850 Additionally, the file
851 .Pa /etc/ssh/ssh_known_hosts
852 is automatically checked for known hosts.
853 Any new hosts are automatically added to the user's file.
854 If a host's identification ever changes,
856 warns about this and disables password authentication to prevent
857 server spoofing or man-in-the-middle attacks,
858 which could otherwise be used to circumvent the encryption.
860 .Cm StrictHostKeyChecking
861 option can be used to control logins to machines whose
862 host key is not known or has changed.
864 When the user's identity has been accepted by the server, the server
865 either executes the given command, or logs into the machine and gives
866 the user a normal shell on the remote machine.
867 All communication with
868 the remote command or shell will be automatically encrypted.
870 If a pseudo-terminal has been allocated (normal login session), the
871 user may use the escape characters noted below.
873 If no pseudo-tty has been allocated,
874 the session is transparent and can be used to reliably transfer binary data.
875 On most systems, setting the escape character to
877 will also make the session transparent even if a tty is used.
879 The session terminates when the command or shell on the remote
880 machine exits and all X11 and TCP connections have been closed.
881 .Sh ESCAPE CHARACTERS
882 When a pseudo-terminal has been requested,
884 supports a number of functions through the use of an escape character.
886 A single tilde character can be sent as
888 or by following the tilde by a character other than those described below.
889 The escape character must always follow a newline to be interpreted as
891 The escape character can be changed in configuration files using the
893 configuration directive or on the command line by the
897 The supported escapes (assuming the default
907 List forwarded connections.
911 at logout when waiting for forwarded connection / X11 sessions to terminate.
913 Display a list of escape characters.
915 Send a BREAK to the remote system
916 (only useful for SSH protocol version 2 and if the peer supports it).
919 Currently this allows the addition of port forwardings using the
925 It also allows the cancellation of existing remote port-forwardings
928 .Fl KR Oo Ar bind_address : Oc Ar port .
930 .Ic !\& Ns Ar command
931 allows the user to execute a local command if the
932 .Ic PermitLocalCommand
935 Basic help is available, using the
939 Request rekeying of the connection
940 (only useful for SSH protocol version 2 and if the peer supports it).
943 Forwarding of arbitrary TCP connections over the secure channel can
944 be specified either on the command line or in a configuration file.
945 One possible application of TCP forwarding is a secure connection to a
946 mail server; another is going through firewalls.
948 In the example below, we look at encrypting communication between
949 an IRC client and server, even though the IRC server does not directly
950 support encrypted communications.
951 This works as follows:
952 the user connects to the remote host using
954 specifying a port to be used to forward connections
955 to the remote server.
956 After that it is possible to start the service which is to be encrypted
957 on the client machine,
958 connecting to the same local port,
961 will encrypt and forward the connection.
963 The following example tunnels an IRC session from client machine
967 .Dq server.example.com :
968 .Bd -literal -offset 4n
969 $ ssh -f -L 1234:localhost:6667 server.example.com sleep 10
970 $ irc -c '#users' -p 1234 pinky 127.0.0.1
973 This tunnels a connection to IRC server
974 .Dq server.example.com ,
980 It doesn't matter which port is used,
981 as long as it's greater than 1023
982 (remember, only root can open sockets on privileged ports)
983 and doesn't conflict with any ports already in use.
984 The connection is forwarded to port 6667 on the remote server,
985 since that's the standard port for IRC services.
991 and the remote command
993 is specified to allow an amount of time
994 (10 seconds, in the example)
995 to start the service which is to be tunnelled.
996 If no connections are made within the time specified,
1004 (or see the description of the
1010 and the user is using X11 (the
1012 environment variable is set), the connection to the X11 display is
1013 automatically forwarded to the remote side in such a way that any X11
1014 programs started from the shell (or command) will go through the
1015 encrypted channel, and the connection to the real X server will be made
1016 from the local machine.
1017 The user should not manually set
1019 Forwarding of X11 connections can be
1020 configured on the command line or in configuration files.
1026 will point to the server machine, but with a display number greater than zero.
1027 This is normal, and happens because
1031 X server on the server machine for forwarding the
1032 connections over the encrypted channel.
1035 will also automatically set up Xauthority data on the server machine.
1036 For this purpose, it will generate a random authorization cookie,
1037 store it in Xauthority on the server, and verify that any forwarded
1038 connections carry this cookie and replace it by the real cookie when
1039 the connection is opened.
1040 The real authentication cookie is never
1041 sent to the server machine (and no cookies are sent in the plain).
1047 (or see the description of the
1052 the user is using an authentication agent, the connection to the agent
1053 is automatically forwarded to the remote side.
1054 .Sh VERIFYING HOST KEYS
1055 When connecting to a server for the first time,
1056 a fingerprint of the server's public key is presented to the user
1058 .Cm StrictHostKeyChecking
1060 Fingerprints can be determined using
1063 .Dl $ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key
1065 If the fingerprint is already known, it can be matched
1066 and the key can be accepted or rejected.
1067 Because of the difficulty of comparing host keys
1068 just by looking at hex strings,
1069 there is also support to compare host keys visually,
1076 a small ASCII graphic gets displayed on every login to a server, no matter
1077 if the session itself is interactive or not.
1078 By learning the pattern a known server produces, a user can easily
1079 find out that the host key has changed when a completely different pattern
1081 Because these patterns are not unambiguous however, a pattern that looks
1082 similar to the pattern remembered only gives a good probability that the
1083 host key is the same, not guaranteed proof.
1085 To get a listing of the fingerprints along with their random art for
1086 all known hosts, the following command line can be used:
1088 .Dl $ ssh-keygen -lv -f ~/.ssh/known_hosts
1090 If the fingerprint is unknown,
1091 an alternative method of verification is available:
1092 SSH fingerprints verified by DNS.
1093 An additional resource record (RR),
1095 is added to a zonefile
1096 and the connecting client is able to match the fingerprint
1097 with that of the key presented.
1099 In this example, we are connecting a client to a server,
1100 .Dq host.example.com .
1101 The SSHFP resource records should first be added to the zonefile for
1103 .Bd -literal -offset indent
1104 $ ssh-keygen -r host.example.com.
1107 The output lines will have to be added to the zonefile.
1108 To check that the zone is answering fingerprint queries:
1110 .Dl $ dig -t SSHFP host.example.com
1112 Finally the client connects:
1113 .Bd -literal -offset indent
1114 $ ssh -o "VerifyHostKeyDNS ask" host.example.com
1116 Matching host key fingerprint found in DNS.
1117 Are you sure you want to continue connecting (yes/no)?
1121 .Cm VerifyHostKeyDNS
1124 for more information.
1125 .Sh SSH-BASED VIRTUAL PRIVATE NETWORKS
1127 contains support for Virtual Private Network (VPN) tunnelling
1130 network pseudo-device,
1131 allowing two networks to be joined securely.
1134 configuration option
1136 controls whether the server supports this,
1137 and at what level (layer 2 or 3 traffic).
1139 The following example would connect client network 10.0.50.0/24
1140 with remote network 10.0.99.0/24 using a point-to-point connection
1141 from 10.1.1.1 to 10.1.1.2,
1142 provided that the SSH server running on the gateway to the remote network,
1143 at 192.168.1.15, allows it.
1146 .Bd -literal -offset indent
1147 # ssh -f -w 0:1 192.168.1.15 true
1148 # ifconfig tun0 10.1.1.1 10.1.1.2 netmask 255.255.255.252
1149 # route add 10.0.99.0/24 10.1.1.2
1153 .Bd -literal -offset indent
1154 # ifconfig tun1 10.1.1.2 10.1.1.1 netmask 255.255.255.252
1155 # route add 10.0.50.0/24 10.1.1.1
1158 Client access may be more finely tuned via the
1159 .Pa /root/.ssh/authorized_keys
1160 file (see below) and the
1163 The following entry would permit connections on
1167 and on tun device 2 from user
1172 .Dq forced-commands-only :
1173 .Bd -literal -offset 2n
1174 tunnel="1",command="sh /etc/netstart tun1" ssh-rsa ... jane
1175 tunnel="2",command="sh /etc/netstart tun2" ssh-rsa ... john
1178 Since an SSH-based setup entails a fair amount of overhead,
1179 it may be more suited to temporary setups,
1180 such as for wireless VPNs.
1181 More permanent VPNs are better provided by tools such as
1187 will normally set the following environment variables:
1188 .Bl -tag -width "SSH_ORIGINAL_COMMAND"
1192 variable indicates the location of the X11 server.
1193 It is automatically set by
1195 to point to a value of the form
1199 indicates the host where the shell runs, and
1201 is an integer \*(Ge 1.
1203 uses this special value to forward X11 connections over the secure
1205 The user should normally not set
1208 will render the X11 connection insecure (and will require the user to
1209 manually copy any required authorization cookies).
1211 Set to the path of the user's home directory.
1215 set for compatibility with systems that use this variable.
1217 Set to the path of the user's mailbox.
1221 as specified when compiling
1226 needs a passphrase, it will read the passphrase from the current
1227 terminal if it was run from a terminal.
1230 does not have a terminal associated with it but
1234 are set, it will execute the program specified by
1236 and open an X11 window to read the passphrase.
1237 This is particularly useful when calling
1242 (Note that on some machines it
1243 may be necessary to redirect the input from
1246 .It Ev SSH_AUTH_SOCK
1247 Identifies the path of a
1249 socket used to communicate with the agent.
1250 .It Ev SSH_CONNECTION
1251 Identifies the client and server ends of the connection.
1252 The variable contains
1253 four space-separated values: client IP address, client port number,
1254 server IP address, and server port number.
1255 .It Ev SSH_ORIGINAL_COMMAND
1256 This variable contains the original command line if a forced command
1258 It can be used to extract the original arguments.
1260 This is set to the name of the tty (path to the device) associated
1261 with the current shell or command.
1262 If the current session has no tty,
1263 this variable is not set.
1265 This variable is set to indicate the present time zone if it
1266 was set when the daemon was started (i.e. the daemon passes the value
1267 on to new connections).
1269 Set to the name of the user logging in.
1275 .Pa ~/.ssh/environment ,
1276 and adds lines of the format
1278 to the environment if the file exists and users are allowed to
1279 change their environment.
1280 For more information, see the
1281 .Cm PermitUserEnvironment
1285 .Bl -tag -width Ds -compact
1287 This file is used for host-based authentication (see above).
1288 On some machines this file may need to be
1289 world-readable if the user's home directory is on an NFS partition,
1293 Additionally, this file must be owned by the user,
1294 and must not have write permissions for anyone else.
1296 permission for most machines is read/write for the user, and not
1297 accessible by others.
1300 This file is used in exactly the same way as
1302 but allows host-based authentication without permitting login with
1306 This directory is the default location for all user-specific configuration
1307 and authentication information.
1308 There is no general requirement to keep the entire contents of this directory
1309 secret, but the recommended permissions are read/write/execute for the user,
1310 and not accessible by others.
1312 .It ~/.ssh/authorized_keys
1313 Lists the public keys (RSA/DSA) that can be used for logging in as this user.
1314 The format of this file is described in the
1317 This file is not highly sensitive, but the recommended
1318 permissions are read/write for the user, and not accessible by others.
1321 This is the per-user configuration file.
1322 The file format and configuration options are described in
1324 Because of the potential for abuse, this file must have strict permissions:
1325 read/write for the user, and not accessible by others.
1327 .It ~/.ssh/environment
1328 Contains additional definitions for environment variables; see
1335 Contains the private key for authentication.
1337 contain sensitive data and should be readable by the user but not
1338 accessible by others (read/write/execute).
1340 will simply ignore a private key file if it is accessible by others.
1341 It is possible to specify a passphrase when
1342 generating the key which will be used to encrypt the
1343 sensitive part of this file using 3DES.
1345 .It ~/.ssh/identity.pub
1346 .It ~/.ssh/id_dsa.pub
1347 .It ~/.ssh/id_rsa.pub
1348 Contains the public key for authentication.
1350 sensitive and can (but need not) be readable by anyone.
1352 .It ~/.ssh/known_hosts
1353 Contains a list of host keys for all hosts the user has logged into
1354 that are not already in the systemwide list of known host keys.
1357 for further details of the format of this file.
1360 Commands in this file are executed by
1362 when the user logs in, just before the user's shell (or command) is
1366 manual page for more information.
1368 .It /etc/hosts.equiv
1369 This file is for host-based authentication (see above).
1370 It should only be writable by root.
1372 .It /etc/shosts.equiv
1373 This file is used in exactly the same way as
1375 but allows host-based authentication without permitting login with
1378 .It Pa /etc/ssh/ssh_config
1379 Systemwide configuration file.
1380 The file format and configuration options are described in
1383 .It /etc/ssh/ssh_host_key
1384 .It /etc/ssh/ssh_host_dsa_key
1385 .It /etc/ssh/ssh_host_rsa_key
1386 These three files contain the private parts of the host keys
1387 and are used for host-based authentication.
1388 If protocol version 1 is used,
1390 must be setuid root, since the host key is readable only by root.
1391 For protocol version 2,
1395 to access the host keys,
1396 eliminating the requirement that
1398 be setuid root when host-based authentication is used.
1403 .It /etc/ssh/ssh_known_hosts
1404 Systemwide list of known host keys.
1405 This file should be prepared by the
1406 system administrator to contain the public host keys of all machines in the
1408 It should be world-readable.
1411 for further details of the format of this file.
1414 Commands in this file are executed by
1416 when the user logs in, just before the user's shell (or command) is started.
1419 manual page for more information.
1435 .%T "The Secure Shell (SSH) Protocol Assigned Numbers"
1440 .%T "The Secure Shell (SSH) Protocol Architecture"
1445 .%T "The Secure Shell (SSH) Authentication Protocol"
1450 .%T "The Secure Shell (SSH) Transport Layer Protocol"
1455 .%T "The Secure Shell (SSH) Connection Protocol"
1460 .%T "Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints"
1465 .%T "Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)"
1470 .%T "The Secure Shell (SSH) Session Channel Break Extension"
1475 .%T "The Secure Shell (SSH) Transport Layer Encryption Modes"
1480 .%T "Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol"
1485 .%T "Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol"
1490 .%T "The Secure Shell (SSH) Public Key File Format"
1494 .%T "Hash Visualization: a New Technique to improve Real-World Security"
1498 .%O "International Workshop on Cryptographic Techniques and E-Commerce (CrypTEC '99)"
1501 OpenSSH is a derivative of the original and free
1502 ssh 1.2.12 release by Tatu Ylonen.
1503 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1504 Theo de Raadt and Dug Song
1505 removed many bugs, re-added newer features and
1507 Markus Friedl contributed the support for SSH
1508 protocol versions 1.5 and 2.0.
projects / FreeBSD / releng / 8.1.git / blob