summaryrefslogtreecommitdiff
path: root/ssh.1.in
diff options
context:
space:
mode:
authorDamien Miller <djm@mindrot.org>2000-01-14 15:45:46 +1100
committerDamien Miller <djm@mindrot.org>2000-01-14 15:45:46 +1100
commit34132e54cbd221d17d373fc54f4e3f7b85727f7f (patch)
tree7c73917b1082ff91786f9e02d25b853bedd1d472 /ssh.1.in
parent25e4256ad4f453d8a7c1866243ec1984f859b1de (diff)
- Merged OpenBSD IPv6 patch:
- [sshd.c sshd.8 sshconnect.c ssh.h ssh.c servconf.h servconf.c scp.1] [scp.c packet.h packet.c login.c log.c canohost.c channels.c] [hostfile.c sshd_config] ipv6 support: mostly gethostbyname->getaddrinfo/getnameinfo, new features: sshd allows multiple ListenAddress and Port options. note that libwrap is not IPv6-ready. (based on patches from fujiwara@rcac.tdi.co.jp) - [ssh.c canohost.c] more hints (hints.ai_socktype=SOCK_STREAM) for getaddrinfo, from itojun@ - [channels.c] listen on _all_ interfaces for X11-Fwd (hints.ai_flags = AI_PASSIVE) - [packet.h] allow auth-kerberos for IPv4 only - [scp.1 sshd.8 servconf.h scp.c] document -4, -6, and 'ssh -L 2022/::1/22' - [ssh.c] 'ssh @host' is illegal (null user name), from karsten@gedankenpolizei.de - [sshconnect.c] better error message - [sshd.c] allow auth-kerberos for IPv4 only - Big IPv6 merge: - Cleanup overrun in sockaddr copying on RHL 6.1 - Replacements for getaddrinfo, getnameinfo, etc based on versions from patch from KIKUCHI Takahiro <kick@kyoto.wide.ad.jp> - Replacement for missing structures on systems that lack IPv6 - record_login needed to know about AF_INET6 addresses - Borrowed more code from OpenBSD: rresvport_af and requisites
Diffstat (limited to 'ssh.1.in')
-rw-r--r--ssh.1.in22
1 files changed, 18 insertions, 4 deletions
diff --git a/ssh.1.in b/ssh.1.in
index e19f87e13..d2ac0f2c2 100644
--- a/ssh.1.in
+++ b/ssh.1.in
@@ -9,7 +9,7 @@
9.\" 9.\"
10.\" Created: Sat Apr 22 21:55:14 1995 ylo 10.\" Created: Sat Apr 22 21:55:14 1995 ylo
11.\" 11.\"
12.\" $Id: ssh.1.in,v 1.1 1999/12/26 22:23:58 damien Exp $ 12.\" $Id: ssh.1.in,v 1.2 2000/01/14 04:45:51 damien Exp $
13.\" 13.\"
14.Dd September 25, 1999 14.Dd September 25, 1999
15.Dt SSH 1 15.Dt SSH 1
@@ -24,7 +24,7 @@
24.Op Ar command 24.Op Ar command
25.Pp 25.Pp
26.Nm ssh 26.Nm ssh
27.Op Fl afgknqtvxCPX 27.Op Fl afgknqtvxCPX46
28.Op Fl c Ar blowfish | 3des 28.Op Fl c Ar blowfish | 3des
29.Op Fl e Ar escape_char 29.Op Fl e Ar escape_char
30.Op Fl i Ar identity_file 30.Op Fl i Ar identity_file
@@ -396,9 +396,13 @@ by allocating a socket to listen to
396on the local side, and whenever a connection is made to this port, the 396on the local side, and whenever a connection is made to this port, the
397connection is forwarded over the secure channel, and a connection is 397connection is forwarded over the secure channel, and a connection is
398made to 398made to
399.Ar host:hostport 399.Ar host
400port
401.Ar hostport
400from the remote machine. Port forwardings can also be specified in the 402from the remote machine. Port forwardings can also be specified in the
401configuration file. Only root can forward privileged ports. 403configuration file. Only root can forward privileged ports.
404IPv6 addresses can be specified with an alternative syntax:
405.Ar port/host/hostport
402.It Fl R Ar port:host:hostport 406.It Fl R Ar port:host:hostport
403Specifies that the given port on the remote (server) host is to be 407Specifies that the given port on the remote (server) host is to be
404forwarded to the given host and port on the local side. This works 408forwarded to the given host and port on the local side. This works
@@ -407,10 +411,20 @@ by allocating a socket to listen to
407on the remote side, and whenever a connection is made to this port, the 411on the remote side, and whenever a connection is made to this port, the
408connection is forwarded over the secure channel, and a connection is 412connection is forwarded over the secure channel, and a connection is
409made to 413made to
410.Ar host:hostport 414.Ar host
415port
416.Ar hostport
411from the local machine. Port forwardings can also be specified in the 417from the local machine. Port forwardings can also be specified in the
412configuration file. Privileged ports can be forwarded only when 418configuration file. Privileged ports can be forwarded only when
413logging in as root on the remote machine. 419logging in as root on the remote machine.
420.It Fl 4
421Forces
422.Nm
423to use IPv4 addresses only.
424.It Fl 6
425Forces
426.Nm
427to use IPv6 addresses only.
414.El 428.El
415.Sh CONFIGURATION FILES 429.Sh CONFIGURATION FILES
416.Nm 430.Nm