KEX Warn default option change force automation developers to have to recompile their applications
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?
Thanks
Niklas
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?
Thanks
Niklas