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
Date:	Tue, 24 Apr 2001 14:53:06 +0200
From:	Corinna Vinschen <cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: SSHD pubkey authentication
Message-ID:	<20010424145306.H31606@cygbert.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3AE56537 DOT 42ABD5EB AT lapo DOT it>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<3AE56537.42ABD5EB@lapo.it>; from lapo@lapo.it on Tue, Apr 24, 2001 at 01:36:23PM +0200

On Tue, Apr 24, 2001 at 01:36:23PM +0200, Lapo Luchini wrote:
> It is possible to use pubkey authentication on NT?
> I played a lot with ntsec,nontsec,ntea,nontea starting serrvice as
> SYSTEM or as administrator
> 
> Result is that the SYSTEM user can't access
> /home/*/.ssh/authorized_keys[2] no matter the modes or owners, only way
> to use pubkey auth is to start the service as the user that wants to
> connect, not a real solution..
> 
> As anyone got better?

The reason is the restriction for changing user context on NT/W2K.
You can do this only by providing the password of that user, even
if the process is running under LocalSystem account.

> I mean using the OpenSSH distro available now.

I don't understand what you try to say with that sentence.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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

- Raw text -