Mailing List Archive: openssh-2.0beta ssh_config Protocol parsing error.

openssh-2.0beta ssh_config Protocol parsing error.

May 5, 2000, 1:21 AM

Post #1 of 3 (942 views)

Hello all,

It seems that openssh-2.0beta's ssh doesn't parse /etc/ssh/ssh_config (or
equivalent) properly. If I add e.g. 'Protocol 2,1' there, ssh will just
complain '/etc/ssh/ssh_config line 30: garbage at end of line.'. I've
tried changing the line, etc. but the error remains.

True enough, README.openssh2 only mentions ~/.ssh/config, but IMO this
must have been an oversight or something :)

Running it on Redhat 5.1 w/ openssl-0.95a.

Also, I didn't see any option to turn off those messages about 1023 vs
1024 bit key size bug in SSH inc.'s ssh. I'm not really interested in
getting them, and after a while they get boring -- and I don't think I'm
alone here. :)

Regards,

--
Pekka Savola "Tell me of difficulties surmounted,
Pekka.Savola@netcore.fi not those you stumble over and fall"

Re: openssh-2.0beta ssh_config Protocol parsing error. [ In reply to ]

markus.friedl at informatik

May 5, 2000, 6:56 AM

Post #2 of 3 (909 views)

Permalink

On Fri, May 05, 2000 at 12:21:47PM +0300, Pekka Savola wrote:
> It seems that openssh-2.0beta's ssh doesn't parse /etc/ssh/ssh_config (or
> equivalent) properly. If I add e.g. 'Protocol 2,1' there, ssh will just
> complain '/etc/ssh/ssh_config line 30: garbage at end of line.'. I've
> tried changing the line, etc. but the error remains.

options are parsed independent from the filename.

> Also, I didn't see any option to turn off those messages about 1023 vs
> 1024 bit key size bug in SSH inc.'s ssh. I'm not really interested in
> getting them, and after a while they get boring -- and I don't think I'm
> alone here. :)

-q should turn the message off. BTW, why not replace the broken keys?

-markus

Re: openssh-2.0beta ssh_config Protocol parsing error. [ In reply to ]

pekkas at netcore

May 5, 2000, 2:12 PM

Post #3 of 3 (917 views)

Permalink

> On Fri, May 05, 2000 at 12:21:47PM +0300, Pekka Savola wrote:
> > It seems that openssh-2.0beta's ssh doesn't parse /etc/ssh/ssh_config (or
> > equivalent) properly. If I add e.g. 'Protocol 2,1' there, ssh will just
> > complain '/etc/ssh/ssh_config line 30: garbage at end of line.'. I've
> > tried changing the line, etc. but the error remains.
>
> options are parsed independent from the filename.

Ok, I didn't check ~/.ssh/config because I believed README.openssh2 and
thought it would of course work ;)

Anyway:
---
pekkas: /home/pekkas/.ssh$ more config
Protocol 1
pekkas: /home/pekkas/.ssh$ ssh box2.test
/home/pekkas/.ssh/config line 1: garbage at end of line.
---

Protocol isn't recognized. It will work with 'ssh -o "Protocol 2"' or
'ssh -2' though.

> > Also, I didn't see any option to turn off those messages about 1023 vs
> > 1024 bit key size bug in SSH inc.'s ssh. I'm not really interested in
> > getting them, and after a while they get boring -- and I don't think I'm
> > alone here. :)
>
> -q should turn the message off. BTW, why not replace the broken keys?

That'd require contacting all remote systems with that problem, reassuring
replacing the keys is OK, etc. It's a little too much hassle for so
little gain.

-q option is nice, but it does suppress some other messages too -- even
some you might want to see if they'd come across. Some option, like
WarnAboutWrongHostKeysize, in ssh_config would probably be nice.

Regards,
--
Pekka Savola "Tell me of difficulties surmounted,
Pekka.Savola@netcore.fi not those you stumble over and fall"