View | Details | Raw Unified | Return to bug 1077
Collapse All | Expand All

(-)ssh.1 (-3 / +39 lines)
Lines 47-53 Link Here
47
.Op Fl 1246AaCfgkMNnqsTtVvXxY
47
.Op Fl 1246AaCfgkMNnqsTtVvXxY
48
.Op Fl b Ar bind_address
48
.Op Fl b Ar bind_address
49
.Op Fl c Ar cipher_spec
49
.Op Fl c Ar cipher_spec
50
.Op Fl D Ar port
50
.Oo Fl D\ \&
51
.Sm off
52
.Oo Ar bind_address : Oc
53
.Ar port
54
.Sm on
55
.Oc
51
.Op Fl e Ar escape_char
56
.Op Fl e Ar escape_char
52
.Op Fl F Ar configfile
57
.Op Fl F Ar configfile
53
.Op Fl i Ar identity_file
58
.Op Fl i Ar identity_file
Lines 494-506 The default is Link Here
494
    arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
499
    arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
495
    aes192-ctr,aes256-ctr''
500
    aes192-ctr,aes256-ctr''
496
.Ed
501
.Ed
497
.It Fl D Ar port
502
.It Fl D Xo
503
.Sm off
504
.Oo Ar bind_address : Oc
505
.Ar port
506
.Sm on
507
.Xc
498
Specifies a local
508
Specifies a local
499
.Dq dynamic
509
.Dq dynamic
500
application-level port forwarding.
510
application-level port forwarding.
501
This works by allocating a socket to listen to
511
This works by allocating a socket to listen to
502
.Ar port
512
.Ar port
503
on the local side, and whenever a connection is made to this port, the
513
on the local side, optionally bound to the specified
514
.Ar bind_address .
515
Whenever a connection is made to this port, the
504
connection is forwarded over the secure channel, and the application
516
connection is forwarded over the secure channel, and the application
505
protocol is then used to determine where to connect to from the
517
protocol is then used to determine where to connect to from the
506
remote machine.
518
remote machine.
Lines 509-514 Currently the SOCKS4 and SOCKS5 protocol Link Here
509
will act as a SOCKS server.
521
will act as a SOCKS server.
510
Only root can forward privileged ports.
522
Only root can forward privileged ports.
511
Dynamic port forwardings can also be specified in the configuration file.
523
Dynamic port forwardings can also be specified in the configuration file.
524
.Pp
525
IPv6 addresses can be specified with an alternative syntax:
526
.Sm off
527
.Xo
528
.Op Ar bind_address No /
529
.Ar port
530
.Xc
531
.Sm on
532
or by enclosing the address in square brackets.
533
Only the superuser can forward privileged ports.
534
By default, the local port is bound in accordance with the
535
.Cm GatewayPorts
536
setting.
537
However, an explicit
538
.Ar bind_address
539
may be used to bind the connection to a specific address.
540
The
541
.Ar bind_address
542
of
543
.Dq localhost
544
indicates that the listening port be bound for local use only, while an
545
empty address or
546
.Sq *
547
indicates that the port should be available from all interfaces.
512
.It Fl e Ar ch | ^ch | none
548
.It Fl e Ar ch | ^ch | none
513
Sets the escape character for sessions with a pty (default:
549
Sets the escape character for sessions with a pty (default:
514
.Ql ~ ) .
550
.Ql ~ ) .
(-)ssh_config.5 (-1 / +23 lines)
Lines 320-326 Specifies that a TCP/IP port on the loca Link Here
320
over the secure channel, and the application
320
over the secure channel, and the application
321
protocol is then used to determine where to connect to from the
321
protocol is then used to determine where to connect to from the
322
remote machine.
322
remote machine.
323
The argument must be a port number.
323
.Pp
324
The argument must be
325
.Sm off
326
.Oo Ar bind_address : Oc Ar port .
327
.Sm on
328
IPv6 addresses can be specified by enclosing addresses in square brackets or
329
by using an alternative syntax:
330
.Oo Ar bind_address Ns / Oc Ns Ar port .
331
By default, the local port is bound in accordance with the
332
.Cm GatewayPorts
333
setting.
334
However, an explicit
335
.Ar bind_address
336
may be used to bind the connection to a specific address.
337
The
338
.Ar bind_address
339
of
340
.Dq localhost
341
indicates that the listening port be bound for local use only, while an
342
empty address or
343
.Sq *
344
indicates that the port should be available from all interfaces.
345
.Pp
324
Currently the SOCKS4 and SOCKS5 protocols are supported, and
346
Currently the SOCKS4 and SOCKS5 protocols are supported, and
325
.Nm ssh
347
.Nm ssh
326
will act as a SOCKS server.
348
will act as a SOCKS server.

Return to bug 1077