dbclient fails to honor -o options
Ravi Parimi
rparimi at gmail.com
Tue Oct 7 10:57:55 WST 2014
Hello Dropbear-er's
I'm running Dropbear v2014.64 on embedded linux and noticed that
dbclient doesn't recognize -o options that work with the normal ssh
client. For e.g:
loader# scp -o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null 10.11.0.20:/storage/file.txt /tmp/
WARNING: Ignoring unknown argument '-oStrictHostKeyChecking=no'
WARNING: Ignoring unknown argument '-oUserKnownHostsFile=/dev/null'
Host '10.11.0.20' is not in the trusted hosts file.
(ecdsa-sha2-nistp256 fingerprint md5
55:72:5e:c5:57:25:a9:c6:3a:37:a5:a9:6e:12:95:a1)
Do you want to continue connecting? (y/n)
The usage string, however, shows that -o is supported.
loader# scp -v
usage: scp [-1246BCpqrv] [-c cipher] [-F ssh_config] [-i identity_file]
[-l limit] [-o ssh_option] [-P port] [-S program]
[[user@]host1:]file1 [...] [[user@]host2:]file2
Next, I created a sample ssh_config file:
loader# cat /.ssh/config
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
And asked scp to read it, but that doesn't work:
loader# scp -F /.ssh/config 10.11.0.20:/storage/file.txt /tmp/
Dropbear v2014.64
Has anyone had luck with getting either of the above options to work?
thanks
More information about the Dropbear
mailing list