reporting a vulnerability
I would want to keep embargo on the issue while the authors triage the issue, so posting it to this forum likely isn't a good idea.
Advertisement
Advertisement
I'll consider it.Any chance this is being backported to 5.13?
Advertisement
I'll consider it.Any chance this is being backported to 5.13?
But to be honest, this is such a negligible problem.
Are you not trusting your server?
And are you actually using SCP protocol at all?
I'll consider it.Any chance this is being backported to 5.13?
But to be honest, this is such a negligible problem.
Are you not trusting your server?
And are you actually using SCP protocol at all?
The primary reason I ask is that version 14 is still considered a release candidate, and this is a product deployed widely in our organization. We can’t speak to what sites are users are connecting, or trusted.
I have fixed the problem in the 5.13 branch. WinSCP 5.13.8 will probably be released the next week.Any update if this could possibly be released in 5.13?
I have fixed the problem in the 5.13 branch. WinSCP 5.13.8 will probably be released the next week.Any update if this could possibly be released in 5.13?
https://winscp.net/eng/docs/history?a=5.13.8
Advertisement
You can post new topics in this forum