我们最近为OpenSSH应用了供应商提供的补丁.该补丁禁用了一些密钥交换协议以响应最近的Logjam攻击.应用此补丁后,我们有一些供应商,我们无法通过sftp交换文件,因为连接协商失败(可能是由于弃用的密钥交换算法).
我想在与供应商交谈之前验证我们看到的一些事情.以下是与其中一个问题供应商(添加的行号)的示例SSH会话：
# ssh -vv user@host.domain.com 01 OpenSSH_6.2p2,OpenSSL 0.9.8j-fips 07 Jan 2009 02 debug1: Reading configuration data /etc/ssh/ssh_config 03 debug1: /etc/ssh/ssh_config line 20: Applying options for * 04 debug2: ssh_connect: needpriv 0 05 debug1: Connecting to host.domain.com [1.2.3.4] port 22. 06 debug1: Connection established. 07 debug1: permanently_set_uid: 0/0 08 debug1: identity file /root/.ssh/id_rsa type -1 09 debug1: identity file /root/.ssh/id_rsa-cert type -1 10 debug1: identity file /root/.ssh/id_dsa type -1 11 debug1: identity file /root/.ssh/id_dsa-cert type -1 12 debug1: identity file /root/.ssh/id_ecdsa type -1 13 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 14 debug1: Enabling compatibility mode for protocol 2.0 15 debug1: Local version string SSH-2.0-OpenSSH_6.2 16 debug1: Remote protocol version 2.0,remote software version GXSSSHD_Comments 17 debug1: no match: GXSSSHD_Comments 18 debug2: fd 3 setting O_NONBLOCK 19 debug1: SSH2_MSG_KEXINIT sent 20 debug1: SSH2_MSG_KEXINIT received 21 debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 22 debug2: kex_parse_kexinit: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa,ssh-dss 23 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se 24 debug2: kex_parse_kexinit: aes128-ctr,rijndael-cbc@lysator.liu.se 25 debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 26 debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-md5-96 27 debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib 28 debug2: kex_parse_kexinit: none,zlib 29 debug2: kex_parse_kexinit: 30 debug2: kex_parse_kexinit: 31 debug2: kex_parse_kexinit: first_kex_follows 0 32 debug2: kex_parse_kexinit: reserved 0 33 debug2: kex_parse_kexinit: diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha256 34 debug2: kex_parse_kexinit: ssh-dss,ssh-rsa 35 debug2: kex_parse_kexinit: aes128-cbc,3des-ctr,aes128-ctr,arcfour128 36 debug2: kex_parse_kexinit: aes128-cbc,arcfour128 37 debug2: kex_parse_kexinit: hmac-md5,hmac-md5-96,hmac-sha256,hmac-sha256@ssh.com 38 debug2: kex_parse_kexinit: hmac-md5,hmac-sha256@ssh.com 39 debug2: kex_parse_kexinit: none,zlib 40 debug2: kex_parse_kexinit: none,zlib 41 debug2: kex_parse_kexinit: 42 debug2: kex_parse_kexinit: 43 debug2: kex_parse_kexinit: first_kex_follows 0 44 debug2: kex_parse_kexinit: reserved 0 45 debug2: mac_setup: found hmac-md5 46 debug1: kex: server->client aes128-ctr hmac-md5 none 47 debug2: mac_setup: found hmac-md5 48 debug1: kex: client->server aes128-ctr hmac-md5 none 49 debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1536<3072<8192) sent 50 debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP 51 DH_GEX group out of range: 1536 !< 1024 !< 8192`
因此,在密钥交换协商期间,客户端和服务器交换它们支持的算法列表(第21和33行).他们同意使用两个列表中的第一个匹配项,在本例中为diffie-hellman-group-exchange-sha1.据我了解,该算法支持客户端和服务器必须协商的一系列位长度.在正常情况下,客户端和服务器就比特长度和交换密钥达成一致,利用来自模数文件的DH prime,例如,/ etc / ssh / moduli(我知道这最后一句话非常“外行说话”,但这大致是它的长短).
在这种情况下,我认为我看到的是比特长度协商失败.在第49行,客户端(我)说“我支持1536和8192之间的位长,并希望使用3072位.”但是,服务器回复并说“我只支持1024位”.客户放弃了,并说：“我不能跟你说话.”这是对这里发生的事情的合理描述吗？
据我所知,问题完全在服务器端(此时我们不会像diffie-hellman-group1-sha1那样协商一个较弱的算法).必须修改服务器以在密钥交换过程中支持更大的比特长度.
在继续之前,我想确保我正确理解这一点.输入表示赞赏.
解决方法
如果要使用较新的OpenSSH连接到已弃用的服务器：
ssh -o KexAlgorithms=diffie-hellman-group14-sha1 -o HostKeyAlgorithms=+ssh-dss my.host.com
如果你想看看发生了什么,添加-v,如果它仍然不起作用,则-o HostKeyAlgorithms = ssh-dss：
ssh -v -o HostKeyAlgorithms=ssh-dss -o KexAlgorithms=diffie-hellman-group14-sha1 my.host.com
当然,您也可以编辑/ etc / ssh / ssh_config或〜/ .ssh / ssh_config,并添加：
Host my.host.com *.myinsecure.net 192.168.1.* 192.168.2.*
HostKeyAlgorithms ssh-dss
KexAlgorithms diffie-hellman-group1-sha1
https://forum.ctwug.za.net/t/fyi-openssh-to-access-rbs-openssh-7/6069在Mikrotik Routerboards上提到了以下修复：
/ip ssh set strong-crypto=yes
(注意这一点,因为在寻找类似的错误消息时,这个答案也出现在网络搜索上.)
如果你想在不编辑ssh_config或更新SSH服务器的情况下通过Git使用它：
GIT_SSH="ssh -oHostKeyAlgorithms=+ssh-dss -oKexAlgorithms=diffie-hellman-group14-sha1" git clone ssh://user@host/path-to-repository
