aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSteve Sakoman <steve@sakoman.com>2021-10-18 13:17:29 -1000
committerSteve Sakoman <steve@sakoman.com>2021-10-19 04:04:49 -1000
commit5fc4f7896fb7af94cd0eeb6370128c861193a6ea (patch)
treed38da1bc3c086152ea6a67ccca780527e454f044
parent917f800368c6d452670d3ccf74057afae98013b0 (diff)
downloadopenembedded-core-contrib-stable/dunfell-next.tar.gz
openembedded-core-contrib-stable/dunfell-next.tar.bz2
openembedded-core-contrib-stable/dunfell-next.zip
target/ssh.py: add HostKeyAlgorithms option to test commandsstable/dunfell-next
After recent updates to the autobuilder tumbleweed workers there are tests where the client and server fail to agree on a public key algorithm for host authentication: DEBUG: [Running]$ ssh -l root -o PubkeyAcceptedKeyTypes=+ssh-rsa -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=VERBOSE 192.168.7.6 export PATH=/usr/sbin:/sbin:/usr/bin:/bin; uname -a DEBUG: time: 1634578090.4632802, endtime: 1634578390.4592378 DEBUG: Partial data from SSH call: Unable to negotiate with 192.168.7.6 port 22: no matching host key type found. Their offer: ssh-rsa This appears to be an issue with recent versions of shh. Add -o HostKeyAlgorithms=+ssh-rsa to command invocation as suggested at: http://www.openssh.com/legacy.html Signed-off-by: Steve Sakoman <steve@sakoman.com>
-rw-r--r--meta/lib/oeqa/core/target/ssh.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/meta/lib/oeqa/core/target/ssh.py b/meta/lib/oeqa/core/target/ssh.py
index aefb576805..af4a67f266 100644
--- a/meta/lib/oeqa/core/target/ssh.py
+++ b/meta/lib/oeqa/core/target/ssh.py
@@ -34,6 +34,7 @@ class OESSHTarget(OETarget):
self.timeout = timeout
self.user = user
ssh_options = [
+ '-o', 'HostKeyAlgorithms=+ssh-rsa',
'-o', 'UserKnownHostsFile=/dev/null',
'-o', 'StrictHostKeyChecking=no',
'-o', 'LogLevel=ERROR'