X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<loom.20100110T225559-377@post.gmane.org>
References:	<18e742db1001041142j5322d164t2a83f2a3ef0138d4 AT mail DOT gmail DOT com> <loom DOT 20100105T001743-66 AT post DOT gmane DOT org> <4B427F97 DOT 6030806 AT cygwin DOT com> <loom DOT 20100106T132435-551 AT post DOT gmane DOT org> <4B44A50E DOT 2010007 AT cygwin DOT com> <loom DOT 20100106T212032-94 AT post DOT gmane DOT org> <loom DOT 20100110T225559-377 AT post DOT gmane DOT org>
Date:	Mon, 11 Jan 2010 12:53:27 -0500
Message-ID:	<aed63dd41001110953t7ad7b61fveff1dd52c41a883b@mail.gmail.com>
Subject:	Re: 1.7.1: problem with public key authentication on domain accounts
From:	Greg Fury <gregfury AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Sun, Jan 10, 2010 at 5:26 PM, Thomas Nisbach <nisbach AT cityweb DOT de> wrote:

> Here is my SOLUTION and what I additionally found:
> Using LSA-package (running cyglsa-config script and reboot) is (the only?)
> solution (Larry recommended, too)!
> I read Corinna's message (also linked by CYGWIN User's Guide,
> http://cygwin.com/ml/cygwin-developers/2006-11/msg00000.html). Here she
> mentions that it is necessary to use LSA or a special user account like
> sshd_server. Before updating to CYGWIN 1.7.1 I did not use LSA or a special
> user account. Everything run fine since mid of 2006 and all CYGWIN updates in
> between. I still do not understand what the difference in 1.7.1 is. Therefore
> here my investigations:
>
<snip>
>
> What I found (without LSA configured):
> Changing my login shell to /usr/bin/telnet made it possible to make some
> tests. Telnet was started by sshd on my login host but it e.g. was not
> possible to run local commands via "!" command (...could not load ws2_32,
> Win32 error 126). Via Sysinternals process explorer I found a lot of
> privileges missing on the forked sshd and telnet process. I guess the
> privilege to modify the PATH is missing because PATH of the telnet process was
> empty (resulting in the error message above?)
>
> Conclusion: Should there be a recommandation in the User's guid to use LSA
> when updating to 1.7.1 and using services like SSH?
>

This worked for me.  I configured LSA and ssh worked as it did in Cygwin 1.5.

-Greg

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

- Raw text -