Once again: The negotiation of encryption algorithm is failed.

Discussion of open issues, suggestions and bugs regarding network security and data protection solution - SecureBridge
Post Reply
UliBru
Posts: 1
Joined: Tue 15 Sep 2015 09:09

Once again: The negotiation of encryption algorithm is failed.

Post by UliBru » Tue 15 Sep 2015 09:25

Hi,

I'm evaluating SecureBridge and have immediately stumbled into a problem, which has previously discussed here already. But I do not know how to proceed.

I like to use the SFTP client and connect to a Linux system with a running sshd. I have no problem to connect by PuTTY or WinSCP.
But trying to run the demos, of course with the correct connection data, always fails with the error message mentioned in the topic.

I have read about modifying the ciphers accordingly in other discussions here but I have no access to the Linux system. I can't change it.
So why is WinSCP successfully connecting whereas Securebridge fails? There is e.g. no need to change or define the ciphers list in WinSCP.
Can I properly modify the demo program to get it running?

Thanks for any help.

- Uli

ViktorV
Devart Team
Posts: 3168
Joined: Wed 30 Jul 2014 07:16

Re: Once again: The negotiation of encryption algorithm is failed.

Post by ViktorV » Tue 15 Sep 2015 12:00

This error can be raised if setted client encryption algorithms have no compliance with server algorithms.
We will add support for CTR ciphers in the next SecureBridge build, that will be released within a month.

Post Reply