packages/net/sshtunnel, branch masterMirror of packages feedhttps://git.openwrt.org/feed/packages/atom?h=master2023-12-27T17:31:33Zsshtunnel: update to v5.22023-12-27T17:31:33ZSergey Ponomarev2023-12-23T14:57:34Zurn:sha1:9130a94425c65f05d315beb00020633825e5b446
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: simplify command composition2023-12-27T17:31:33ZSergey Ponomarev2023-12-22T21:35:41Zurn:sha1:28e8daf726ee3f5aaec163401c40900ecb69e876
Remove append_params and use shell expressions instead e.g. ${port:+-p $port}.
Note that we can't do that with ProxyCommand because it has to be quoted.
The order of options was changed from more important like hostname to just static -nN.
The CompressionLevel option is removed from SSH2.
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: ProxyCommand option2023-12-27T17:31:33ZSergey Ponomarev2023-12-22T21:27:54Zurn:sha1:d1d1bd60c94e3e23d3bec3895250e0cd812ff250
The ProxyCommand may have spaces so it must be quoted.
So we must use the procd_append_param.
Currently the option is not supported by Dropbear.
But it has -J instead which in OpenSSH means ProxyJump.
So we can't use it to avoid conflict.
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: update version to 5.12023-10-08T09:29:37ZSergey Ponomarev2023-09-20T14:27:45Zurn:sha1:fdaf5309507a591e0837f6314b8c94849fba08db
Make it depends on ether Dropbear dbclient or OpenSSH client
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: allow empty port and user2023-10-08T09:29:37ZSergey Ponomarev2023-06-21T17:01:31Zurn:sha1:1a92dbcf32eec04b7f6de9001b8568911b58039a
A user may have some host configured in the .ssh/config with user and port.
But we anyway have to specify them in the sshtunnel.
The change fixes this
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: add enabled option2023-10-08T09:29:37ZSergey Ponomarev2023-06-21T16:59:28Zurn:sha1:9ea6f35194e888af5402bcecc67d074763758189
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: allow empty remoteaddress2023-10-08T09:29:37ZSergey Ponomarev2023-06-21T16:58:48Zurn:sha1:9dd8a62238d79b94d293c2c1c1631a25eafe98d1
Just empty or * may have some semantic difference on a server
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: StrictHostKeyChecking for Dropbear2023-10-08T09:29:37ZSergey Ponomarev2023-06-03T11:23:33Zurn:sha1:1d9f10a1356df1862bfff4f3031011403ddfe0bd
The dbclient doesn't support the -o StrictHostKeyChecking but it has it's own -y option:
-y Always accept remote host key if unknown
-y -y Don't perform any remote host key checking (caution)
So we can add these options to make the StrictHostKeyChecking working.
The dbclient will ignore -o StrictHostKeyChecking but use the -y or -yy instead.
The only problem is that the -y flag is also used by the openssh-client:
-y Send log information using the syslog(3) system module. By default this information is sent to stderr.
This is not critical and once the dbclient start to support the StrictHostKeyChecking we can remove the -y flag.
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: Use -i $IdentityFile instead of -o IdentityFile=$IdentityFile2023-10-08T09:29:37ZSergey Ponomarev2023-06-03T10:23:35Zurn:sha1:f14dae7bc9ef0db6f6b25e605dc6c963d9417e17
This makes the sshtunnel compatible with Dropbear.
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>
sshtunnel: set StrictHostKeyChecking=accept-new by default2023-10-08T09:29:37ZSergey Ponomarev2023-06-03T10:10:32Zurn:sha1:714c97b012285ce28bc392a7d86a26c8fedd5d3d
Without the option the ssh will propt a user to accept the host key.
So a user should perform a connection manualy and accept before useing the sshtunnel.
The accept-new is a reasonable trade off.
Also the LogLevel is INFO by default.
Signed-off-by: Sergey Ponomarev <stokito@gmail.com>