summaryrefslogtreecommitdiffstats
path: root/scripts/bitbake-prserv-tool
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2015-03-08 12:25:56 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-03-20 11:27:45 +0000
commitad57dab31f5d91327cadac196e8d620bc9df551e (patch)
treed029231ed449572f34095b9d2dd35e6b69baa78a /scripts/bitbake-prserv-tool
parentcb4b07838c267a09ebedba6c30ec25bda2cd11be (diff)
downloadast2050-yocto-poky-ad57dab31f5d91327cadac196e8d620bc9df551e.zip
ast2050-yocto-poky-ad57dab31f5d91327cadac196e8d620bc9df551e.tar.gz
devtool: deploy-target: allow disabling host key checking
If you're testing with multiple images/devices that have the same IP address / hostname then it can be annoying to deal with host key mismatches all of the time. As a MITM attack is unlikely in the local test environment, provide a command line option to pass the appropriate options to scp/ssh to disable the host key checking. Note: if you wish to apply this permanently, the best way is to do it through your ssh configuration e.g. by adding the following to your ~/.ssh/config: Host 192.168.7.2 UserKnownHostsFile=/dev/null StrictHostKeyChecking no (From OE-Core rev: 81dd1319112a99bc38b7a7ced0663918ac5b09a4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/bitbake-prserv-tool')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud