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:	Wed, 28 Mar 2001 10:24:12 -0500 (EST)
From:	Antonio Bemfica <antonio AT axolotl DOT ic DOT gc DOT ca>
To:	cygwin AT cygwin DOT com
Subject:	SSH login problem (only works when login in as user running sshd)
Message-ID:	<Pine.BSF.3.96.1010328100732.36233E-100000@axolotl.ic.gc.ca>
MIME-Version:	1.0

Hello

I am following the thread on SSH login problems (through the archives) and
decided to post a couple of extra findings (no solution, though).

1. Login via SSH works when connecting as the same user who is running
sshd (either as a service or from a prompt):

- "ssh NTserver" will authenticate via password (in my case) and generate
a STATUS_ACCESS_VIOLATION on id.exe immediately after login (will see the
prompt). All further commands will generate the same exception. 

- "ssh -l Administrator NTserver" will authenticate via RSA without
problems (I have the keys in the proper places and allow for it on
sshd_config) and will not generate any exceptions - it all works.

2. Login in as a different user and starting sshd from the command line
(stop the service first) will allow for the reverse of the situation above
(user Administrator will crash on login now, the other user will work). 

I do not have the variable CYGWIN set to ntsec (or anything else) and have
not modified the permissions for any files. This is the latest version of
the distribution.

Antonio


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

- Raw text -