Comment 4 for bug 1468752

The scope of the fix is such that it is non trivial to backport to 1.25. Given the number of people trying to run ssh onto Windows on 1.25 it doesn't feel worth the effort to develop a new fix there.

If we get significant demand that we really do need this, then we can reopen this, but its fairly accurate to say that we don't feel like this bug is worth the development effort at this time. 2.0/1 does have a fix for this, so it isn't an ongoing issue. And we're actively working on a migration path for 1.25 users to 2.X that is likely to be available in the 2.3 timeframe.