Heartbleed bug in OpenSSL
This link connects to detailed information about the bug and which versions of OpenSSL are affected... https://heartbleed.com/
Advertisement
Advertisement
We are working on a fix.
It actually affects even clients:
https://security.stackexchange.com/q/55119/43677
Advertisement
It's not released yet. We plan to release 5.5.3 in few days.Showing on the bug report that you've got it fixed in 5.5.3, but no location as to being able to download the package?
That's true. But WinSCP is also TLS/SSL client, when used with FTP over TLS/SSL. Majority (about 98%) of WinSCP users use SSH (SFTP/SCP) and plain FTP only and are NOT affected!Yes it does, but not SSH (and thus SCP/SFTP) clients because SSH obviously doesn't use TLS heartbeats, so WinSCP and other SSH clients shouldn't be affected at all?
reg query "HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\winscp3_is1" /v "DisplayVersion"
Advertisement
Is there a way to output the version number at the command line from winscp.exe?
C:\test>WinSCP.com /? WinSCP, Version 5.5.2 (Build 4130) Copyright (c) 2000-2014 Martin Prikryl ...
C:\test>WinSCP.com /? WinSCP, Version 5.5.2 (Build 4130) Copyright (c) 2000-2014 Martin Prikryl ...
Advertisement
Yes, you should upgrade. Actually you should always upgrade, when there's a new version available.If I am using WINSCP.EXE command line to connect to an FTPS site, do I need to upgrade to new version due to HeartBleed?
What do you mean by ".NET interop DLL"? Do you mean WinSCP .NET assembly? You always need to upgrade that along with WinSCP. You cannot use different versions of WinSCP and WinSCP .NET assembly together.We use the .NET interop DLL in SSIS packages for FTP and SFTP, is installing version 5.5.3 enough or do we need to also register and upgrade to the latest Interop DLL?
Advertisement
You can post new topics in this forum