1. Home

Product groups

Support

Could not negotiate key exchange algorithm - WeOnlyDo Discussion board

Could not negotiate key exchange algorithm (wodSFTP / wodSFTP.NET / wodSFTPdll)

by movehoon19, Wednesday, December 11, 2024, 01:40 (22 hours, 55 minutes ago)

Hello.

The company is currently sending and receiving SFTP servers using "WeOnlyDo 3.6.1.160".
I recently purchased a company server and started using Red Hat Enterprise Linux 9, but I am inquiring about an error message between connections.

err: Could not negotiate key exchange algorithm.

The program did not set up algorithms separately, and it is in a default state.
The following information is registered on the server side.
Even if all the information is included, it continues to fail.

[admin@K-Sftp-14 ~]$ ssh -Q kex
diffie-hellman-group1-sha1
diffie-hellman-group14-sha1
diffie-hellman-group14-sha256
diffie-hellman-group16-sha512
diffie-hellman-group18-sha512
diffie-hellman-group-exchange-sha1
diffie-hellman-group-exchange-sha256
ecdh-sha2-nistp256
ecdh-sha2-nistp384
ecdh-sha2-nistp521
curve25519-sha256
curve25519-sha256@libssh.org
sntrup761x25519-sha512@openssh.com

[admin@K-Sftp-14 ~]$ ssh -Q cipher
3des-cbc
aes128-cbc
aes192-cbc
aes256-cbc
aes128-ctr
aes192-ctr
aes256-ctr
aes128-gcm@openssh.com
aes256-gcm@openssh.com
chacha20-poly1305@openssh.com

[admin@K-Sftp-14 ~]$ ssh -Q mac
hmac-sha1
hmac-sha1-96
hmac-sha2-256
hmac-sha2-512
hmac-md5
hmac-md5-96
umac-64@openssh.com
umac-128@openssh.com
hmac-sha1-etm@openssh.com
hmac-sha1-96-etm@openssh.com
hmac-sha2-256-etm@openssh.com
hmac-sha2-512-etm@openssh.com
hmac-md5-etm@openssh.com
hmac-md5-96-etm@openssh.com
umac-64-etm@openssh.com
umac-128-etm@openssh.com

I changed the RHEL 9 encryption policy from DEFAULT to LEGACY, and the transmission was possible. The algorithm I used was diffie-hellman-group-exchange-sha256 which I checked through the Log.
However, changing the encryption policy is impossible due to a security risk.

Do I need to upgrade W.o.d?

Please help me.

Thank you.

Post reply
  23 views

Could not negotiate key exchange algorithm

by Jasmine, Wednesday, December 11, 2024, 06:19 (18 hours, 16 minutes ago) @ movehoon19

Hi,
I assume you're using wodSFTP.NET, version from year 2020.

So, yes, before we proceed please try with the latest version to see (and most probably does) problem goes away.
If it persists, we'll see how to help about it, but we can provide help only over latest version.

I hope this helps!
Jasmine

Post reply
  16 views

Your customer service was excellent, and I will look at your products in the future for precisely that reason.

Charles Taylor
InterWeave, Inc.

Thank you so much for your hard work and commitment in producing well thought-out solutions. WeOnlyDo is very committed to customer satisfaction!

Mike McPherson
Nokia Inc.

...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...

Steven Jones
SABIEN project

I really like these products - they are consistently first rate!

David Witten
WWR Development, Inc.

Congratulations on an excellent product and first rate support!

Sander Pool
Rhapsody Networks

...what I really like is that wodSSH and wodSFTP components work excellently and are constantly being improved...

Steven Jones
SABIEN project

...I'm extremely impressed with the product, it represents excellent value for money...

Danny Haworth
Assetdisk

The people at WeOnlyDo are amazing! ... I always get a super fast response from customer service, and the products are great too. Thanks WeOnlyDo

Jeff Hall
Occupational Health Research

We have recently completed a large 1200+ location project where reliable Telnet and SSH connectivity was required. wodSSH worked flawlessly and allowed our staff to complete our project ontime and within budget.

James Sievers
Harbor Technologies

...with WOD's excellent support I was able to bypass Winsock and focus on the task at hand...

Sander Pool
Rhapsody Networks