关于Qt上传下载文件到SSH服务器报错问题,只用账号密码登录(在同一台电脑上，银河麒麟系统)

登录成功,即将进入主界面
正在连接sftp服务器 127.0.0.1 '

SSH 出错:  SSH Protocol error: Server and client capabilities don't match. Client list was: aes128-cbc,3des-cbc
Server list was chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com

服务器和客户端都是银河麒麟操作系统，修改乐sshd_config文件没有效果。

# Package generated configuration file
# See the sshd_config(5) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress 
#ListenAddress 0.0.0.0
#Protocol 2
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes
RSAAuthentication no
PubkeyAuthentication no
#AuthorizedKeysFile .ssh/authorized_keys
# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes
# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no
# Change to no to disable tunnelled clear text passwords
PasswordAuthentication yes
# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no
#MaxStartups 10:30:60
#Banner /etc/issue.net
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password"
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'
UsePAM yes

光看配置没啥问题，主要是服务器和客户端的证书格式不匹配。
一般来说是ssh-client和ssh-server的版本匹配不上，或者源就有问题，可以考虑从几个比较主流的源下载安装openssh官方版本。我之前遇到过太多奇葩问题是魔改版本导致的了，特别是和第三方集成的时候。
保证源是ssh官方的情况下，可能的解决方案如下几种：

打开/etc/ssh/sshd_config，最后添加一行
```
Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc
```
然后重新启动sshd。
你可以尝试删除~/.ssh下的所有主机密钥，两边都重新生成。
双方升级一下openssh，这里所提到的都是比较旧的方案。
如果客户端是自己写的，那么首先检查sdk的版本。再检查一下加密方式，你应该采用的是AES/CBC/PKCS5Padding之一。考虑采用上面提到的aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm,aes256-gcm之一。

在PC机上先删除所有./ssh/id密钥对，然后依次使用 ssh-add -D —> ssh-add （不删除id好像不能ssh-add，不知道为什么），然后ssh-keygen重新生成密钥对，这会再次ssh-add也没错了，先在开发板上设置个密码，使用ssh-cpy-id root@ip将PC上的密钥发布给开发板。将qt里的DEVICE设备全删了，重新新建个就OK了