Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	Sat, 10 Nov 2001 14:35:56 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com, binutils AT sources DOT redhat DOT com
Subject:	Upgraded SSH on sources.redhat.com
Message-ID:	<20011110193556.GA1244@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com, binutils AT sources DOT redhat DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.3.23.1i

If you have CVS checkin privileges on sources.redhat.com you may notice
that ssh can't connect anymore.  This is because I've upgraded the ssh
server on sources.redhat.com to OpenSSH, which understand v2 and v2 ssh
protocol.

So, if you have both keys and your default is to try v2 protocol first,
you won't be able to connect since the client defaults to v2 and there
is no mechanism for dropping back to v1 protocol if v2 fails.

The solution is to add this line to your ~/.ssh/config file:

Host sources.redhat.com
	Protocol 1

Eventually, we'll have a way to upgrade your keys on sources.redhat.com
to ssh2 keys but, for now, the above information is the best way to deal
with this.

Please *don't* send requests to have your keys changed on
sources.redhat.com.  I hope to have an automated way of doing that in a
week or so.

cgf

- Raw text -