Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Marc Poppleton" <marc DOT poppleton AT teamlog DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: SSH key authentification problem
Date: Mon, 19 Jan 2004 13:56:31 +0100
Message-ID: <BKEALJICMGLKMNFJIFACAEBPCAAA.marc.poppleton@teamlog.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <6251234.1074511328@[192.168.0.40]>
X-IsSubscribed: yes

> There is not a lot else the Cygwin list can help with as it appears from
> the verbose output you previously posted that the Cygwin ssh client is
> doing exactly what it should and the problem lies with the Linux sshd
> server.

That all I actually needed to know! :)
I was affraid that something was going wrong on my side, but it seems that
my client is behaving has it should.
Thanks for your help, all of you. I'm forwarding these mail to the admin so
he can figure out what he did wrong.

Marc


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/