Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<035a01c0c2bf$8c644ee0$1d1587a8@deluxe.com>
From:	"CyberZombie" <CyberZombie AT mediaone DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<CCD084B0E779D411A70300508B6622260183853E AT exchukahis02 DOT experian DOT co DOT uk> <20010409153621 DOT G956 AT cygbert DOT vinschen DOT de> <3AD29DC8 DOT 715AB600 AT certum DOT pl> <023501c0c1fb$fe626ff0$1d1587a8 AT deluxe DOT com> <20010411093519 DOT C956 AT cygbert DOT vinschen DOT de>
Subject:	Re: Login/Domains
Date:	Wed, 11 Apr 2001 14:42:25 -0500
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200

From: "Corinna Vinschen" <cygwin AT cygwin DOT com>
> On Tue, Apr 10, 2001 at 03:22:35PM -0500, CyberZombie wrote:
> > still trying to get rsa to work.  I'm now running sshd via inetd
installed
> > as service, running under user ROOT (ROOT is part of a SERVICERUNNER
group
> > w/ all the required privileges).  I'm using "ssh -2 -l root ..." to get
in
> > and it doesn't even ask for my rsa password (yes, the .pub is appended
to
> > the sshd authorized_keys2 file)...
>
> First I began to reply about changing user context and password
> needed but then I saw that you're trying to login as the user
> running the service.
>
> Does "root" have a correct /etc/passwd entry? Especially the home dir
> should be correct. ssh -v should give you a clue.

Root looks correct.  As part of the reinstall, mkpasswd was run -- it looks
fine.  The one change I made (changing shell to /bin/bash) doesn't affect
the outcome, and once I'm connected (via password authentication) everything
works fine.

Here's the part of "ssh -v -2 -l root ..." pertaining to authentication:

debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try pubkey: /home/K02189/.ssh/id_rsa
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is password

I double-checked and the entry in authorized_keys2 is the (generated w/
latest openssh 2 days ago) same as exists on the client.  authorized_keys2
is mode 0600.  Owner of authorized_keys2 is root:None (None is what groups
reports for root).


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -