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
Message-ID: <012701c2febd$9a33df40$a35e893e@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Vince Hoffman" <vince DOT hoffman AT uk DOT circle DOT com>, <cygwin AT cygwin DOT com>
References: <ACEDKBKBMCFCDCBFOOEJKECFCNAA DOT neil AT JAMMConsulting DOT com> <029801c2feb3$ea8f82f0$8801090a AT uk DOT circle DOT com>
Subject: Re: Can't get authorized_keys to work
Date: Wed, 9 Apr 2003 18:29:38 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Vince Hoffman wrote:
> I could be wrong but... shouldnt  id_rsa.pub (and/or id_dsa.pub) be put in
> authorised_keys2 ? (i thought it was ssh1 keys in authorized_keys and ssh2
> keys in authorized_keys2 but that could be my lack of knowlege here) I
tend
> to just use ssh-user-config and add any new keys to the created
> authorized_key/authorized_key2  files.

This was correct in the past, but recent OpenSSH supports either key type in
authorized_keys.


Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/