Re:Critical security updates for Git, Subversion and Mercurial
by peff on Friday August 11, 2017 @09:47AM
(#14989578)
We discussed that, but it wasn't clear that doing so was portable. It works for OpenSSH. It doesn't for PuTTY. We don't know what other implementations people might have as `ssh` on their systems.
[ Parent
| on HN ]
Re:Critical security updates for Git, Subversion and Mercurial
by peterwwillis on Friday August 11, 2017 @12:16PM
(#14991343)
It seems a little risky to assume separate clients/platforms will always interpret command line arguments the same way. At some point when a client breaks compatibility you have to implement methods to support the one-offs, or drop support. So for portability's sake, why not start writing those methods now, and have a generic universal method to fall back on for untested clients/versions?
Or is that really unnecessary?
Re:Critical security updates for Git, Subversion and Mercurial
by avar on Friday August 11, 2017 @02:23PM
(#14992757)
How would a program like git figure out what flavor of "ssh" program is on the system? Keep in mind that it may change while a long-running git command is running.
Re:Critical security updates for Git, Subversion and Mercurial
by pwdisswordfish on Friday August 11, 2017 @12:24PM
(#14991430)
Dropbear[0] doesn't seem to support "--" either.
Re:Critical security updates for Git, Subversion and Mercurial
by luckydude on Friday August 11, 2017 @12:25PM
(#14991448)
What happens if you do the -- fix and then use PuTTY? If it just fails then I'd argue that's OK, PuTTY will get updated as a result of the failure, no?
Re:Critical security updates for Git, Subversion and Mercurial
by pwdisswordfish on Friday August 11, 2017 @12:38PM
(#14991611)
Why do you think Lennart Poettering is hated so much?