Topic "KEX Warn default option change force automation developers to have to recompile their applications"

Author Message
[View user's profile]

Joined: 2016-05-24
Posts: 5
New DH-1 KEX default warning causes exception in automation so they stop working.

The change which was introduced in 5.8.3
"Change: By default, warning is issued when using Diffie-Hellman group 1 key exchange algorithm."
causes problems when using automation as there seems to be no way to specify default warning or using .ini file to avoid this.

I have tested to create same user@site and save it to .ini file without warning, but it is not picked up. Also I don't see any SessionOptions in automation for this.

I know there is RAW settings that can be used, but it is not easy to recompile the automation applications as soon as there is a new WinSCP bug fixed version with some new default setting.

Can we have option to specify default KEX Warn server wide or use .ini file that is in same folder where WinSCP.exe automation is running?
Or can we disable this warning in automation code and only log warning to the log file without throwing exception?

[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 27086
Location: Prague, Czechia
As you have found already, you can use the "KEX" raw setting.

There's no way to change this globally. If you need to allow global changes by an external configuration file, just implement it yourself.

You can easily introduce a configuration file with a key-value syntax like:

And just call sessionOptions.AddRawSettings(key, value) for each pair.

Though actually, you should upgrade your server not to use an obsolete KEX algorithm!

You can post new topics in this forum


What is WinSCP?

It is award-winning SFTP client, SCP client, FTPS client and FTP client integrated into one software program for file transfer to FTP server or secure SFTP server. [More]

And it's free!


About donations

$9   $19   $49   $99

About donations


WinSCP Privacy Policy

WinSCP License