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 <stokito@gmail.com>

diff --git a/net/sshtunnel/files/sshtunnel.init b/net/sshtunnel/files/sshtunnel.init
index 3db8dbb118ce8f380f0c94c822380a19dec8244d..4a23c9fbe74f38723699edb4fc73701aa1cbdcdf 100644 (file)
--- 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")'
 }