From: Sergey Ponomarev Date: Sat, 3 Jun 2023 10:10:32 +0000 (+0300) Subject: sshtunnel: set StrictHostKeyChecking=accept-new by default X-Git-Url: http://git.openwrt.org/?a=commitdiff_plain;h=714c97b012285ce28bc392a7d86a26c8fedd5d3d;p=feed%2Fpackages.git sshtunnel: set StrictHostKeyChecking=accept-new by default 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 --- diff --git a/net/sshtunnel/files/sshtunnel.init b/net/sshtunnel/files/sshtunnel.init index 3db8dbb118..4a23c9fbe7 100644 --- a/net/sshtunnel/files/sshtunnel.init +++ b/net/sshtunnel/files/sshtunnel.init @@ -47,10 +47,10 @@ validate_server_section() { 'Compression:or("yes", "no")' \ 'CompressionLevel:range(1,9)' \ 'IdentityFile:file' \ - 'LogLevel:or("QUIET", "FATAL", "ERROR", "INFO", "VERBOSE", "DEBUG", "DEBUG1", "DEBUG2", "DEBUG3"):INFO' \ + 'LogLevel:or("QUIET", "FATAL", "ERROR", "INFO", "VERBOSE", "DEBUG", "DEBUG1", "DEBUG2", "DEBUG3")' \ 'ServerAliveCountMax:min(1)' \ 'ServerAliveInterval:min(0)' \ - 'StrictHostKeyChecking:or("yes", "no", "accept-new")' \ + 'StrictHostKeyChecking:or("yes", "no", "accept-new"):accept-new' \ 'TCPKeepAlive:or("yes", "no")' \ 'VerifyHostKeyDNS:or("yes", "no")' }