mirror of
https://github.com/clearml/dropbear
synced 2025-06-26 18:17:32 +00:00
- Bump to 0.52
- Clarify that hosts are resolved on the remote end for multihop --HG-- extra : convert_revision : acde944b3ea0b8f673c276d2921c6bb3ede8ddde
This commit is contained in:
@@ -102,7 +102,7 @@ Use the standard input/output of the program \fIproxy_command\fR rather than usi
|
||||
a normal TCP connection. A hostname should be still be provided, as this is used for
|
||||
comparing saved hostkeys.
|
||||
.TP
|
||||
.B \B \fIendhost:endport
|
||||
.B \-B \fIendhost:endport
|
||||
"Netcat-alike" mode, where Dropbear will connect to the given host, then create a
|
||||
forwarded connection to \fIendhost\fR. This will then be presented as dbclient's
|
||||
standard input/output.
|
||||
@@ -117,6 +117,10 @@ ssh/rsh command). A file can be "bounced" through multiple SSH hops, eg
|
||||
|
||||
scp -S dbclient matt@martello,root@wrt,canyons:/tmp/dump .
|
||||
|
||||
Note that hostnames are resolved by the prior hop (so "canyons" would be resolved by the host "wrt")
|
||||
in the example above, the same way as other -L TCP forwarded hosts are. Host keys are
|
||||
checked locally based on the given hostname.
|
||||
|
||||
.SH ENVIRONMENT
|
||||
.TP
|
||||
.B DROPBEAR_PASSWORD
|
||||
|
||||
Reference in New Issue
Block a user