comparison dbclient.1 @ 516:7fc4ba3c1cbb

- Bump to 0.52 - Clarify that hosts are resolved on the remote end for multihop
author Matt Johnston <matt@ucc.asn.au>
date Tue, 11 Nov 2008 14:08:48 +0000
parents fe30d2a2d626
children 52d7301e46bd
comparison
equal deleted inserted replaced
515:fe30d2a2d626 516:7fc4ba3c1cbb
100 .B \-J \fIproxy_command 100 .B \-J \fIproxy_command
101 Use the standard input/output of the program \fIproxy_command\fR rather than using 101 Use the standard input/output of the program \fIproxy_command\fR rather than using
102 a normal TCP connection. A hostname should be still be provided, as this is used for 102 a normal TCP connection. A hostname should be still be provided, as this is used for
103 comparing saved hostkeys. 103 comparing saved hostkeys.
104 .TP 104 .TP
105 .B \B \fIendhost:endport 105 .B \-B \fIendhost:endport
106 "Netcat-alike" mode, where Dropbear will connect to the given host, then create a 106 "Netcat-alike" mode, where Dropbear will connect to the given host, then create a
107 forwarded connection to \fIendhost\fR. This will then be presented as dbclient's 107 forwarded connection to \fIendhost\fR. This will then be presented as dbclient's
108 standard input/output. 108 standard input/output.
109 109
110 Dropbear will also allow multiple "hops" to be specified, separated by commas. In 110 Dropbear will also allow multiple "hops" to be specified, separated by commas. In
114 A port for a host can be specified with a slash (eg matt@martello/44 ). 114 A port for a host can be specified with a slash (eg matt@martello/44 ).
115 This syntax can also be used with scp or rsync (specifying dbclient as the 115 This syntax can also be used with scp or rsync (specifying dbclient as the
116 ssh/rsh command). A file can be "bounced" through multiple SSH hops, eg 116 ssh/rsh command). A file can be "bounced" through multiple SSH hops, eg
117 117
118 scp -S dbclient matt@martello,root@wrt,canyons:/tmp/dump . 118 scp -S dbclient matt@martello,root@wrt,canyons:/tmp/dump .
119
120 Note that hostnames are resolved by the prior hop (so "canyons" would be resolved by the host "wrt")
121 in the example above, the same way as other -L TCP forwarded hosts are. Host keys are
122 checked locally based on the given hostname.
119 123
120 .SH ENVIRONMENT 124 .SH ENVIRONMENT
121 .TP 125 .TP
122 .B DROPBEAR_PASSWORD 126 .B DROPBEAR_PASSWORD
123 A password to use for remote authentication can be specified in the environment 127 A password to use for remote authentication can be specified in the environment