Bug#846165: .../.ssh/config line 127: Bad protocol spec '1'.

2016-11-29 Thread Robert de Bath
Reading back, I may have been a little unclear. It's probably because the arrogance of the openssl people has always aggravated me. (For example the "none" cipher where they, basically, said eveyone else is too stupid to use it sensibily) In this instance they have made the $HOME/.ssh/config

Bug#846165: .../.ssh/config line 127: Bad protocol spec '1'.

2016-11-29 Thread Robert de Bath
That's exactly what I want to do, I have a session in the config file for the ssh1 package. The ssh2 package breaks when it sees it. Now what I would think as a nice polite feature would be for the application that has the '/usr/bin/ssh' name to call the right version of ssh if it sees a 'bad'

Bug#846165: .../.ssh/config line 127: Bad protocol spec '1'.

2016-11-28 Thread Russ Allbery
Robert de Bath writes: > Package: ssh > Version: 1:7.3p1-3 > This error occurs whatever I attempt to connect to, even though the > particular stanza of the config as nothing to do with the host I'm > connecting to. It is obviously inefficient and much too aggressive. > I

Bug#846165: .../.ssh/config line 127: Bad protocol spec '1'.

2016-11-28 Thread Robert de Bath
Package: ssh Version: 1:7.3p1-3 This error occurs whatever I attempt to connect to, even though the particular stanza of the config as nothing to do with the host I'm connecting to. It is obviously inefficient and much too aggressive. I obviously still have a use for v1 as there isn't an ssh