-
Notifications
You must be signed in to change notification settings - Fork 6
[Command] connect
Test provided parameters validity to establish a connection. If a connection is established, identifies the targeted endpoint's Host.
connect [-v|--verbose] [-g|--gateway <gateway>] [<connection>]
-
<connection>: A Connection string. -
<gateway>: An Endpoint.
-
-v|--verbose: print every pivot while connecting -
-g|--gateway <gateway>: force the use of<gateway>as the gateway to connect (instead of automatically calculated path)
If <connection> is provided, test it is working, eventually forcing specified <gateway>.
If <connection> is not provided, use the current workspace options to determine which User and Creds to connect to which Endpoint. If any of these option is not set, try every object in the workspace for the option until a connection is successfully established or all combinations are tested.
connect -v foo:#1@192.168.1.1:22
Test connecting to Endpoint 192.168.1.1:22 with User foo and Creds #1, printing every pivot performed.
connect -g 192.168.3.254:22 bar:#2@192.168.4.15:2222
Test connecting to endpoint 192.168.4.15:2222 using 192.168.3.254:22 as a gateway.
BabooSSH will find an existing working Connection to 192.168.3.254:22, connect to it and using it as a gateway will try to connect to bar:#2@192.168.4.15:2222
set user baz
set endpoint 10.0.15.212:22
connect
As no creds have been specified, BabooSSH will sequentially attempt to connect with User baz to Endpoint 10.0.15.212:22 using every Creds object in the workspace, until a connection is successfully established or all creds are tested. Be careful as this could imply an important number of connection failures, resulting in locked account and alerts.
connect: Without specifying any target either as an argument or in the workspace options, BabooSSH will attemp to log every User using every Creds on every Endpoint. Be careful as this could imply an important number of connection failures, resulting in locked account and alerts.