Message-ID: <COL101-W36BBE2AAC62BCE7BE9CDE4E6110@phx.gbl>
From: Jay K <jay.krell@cornell.edu>
To: cygwin <cygwin@cygwin.com>
Subject: running MS link.exe under Cygwin sshd?
Date: Sat, 1 Aug 2009 04:50:15 +0000
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com


http://social.msdn.microsoft.com/forums/en-US/vcgeneral/thread/eb49be0b-2a8=
c-4d55-8791-17e3cb1364c1
=20
"
This issue is caused because cygwin does not implement a full login process=
. It tries to impersonate, but it looks to me as if it does not make the ne=
cessary call to LsaLogonUser. As a result, the wrong SID is in the token as=
 the primary user. According to filemon, the debug server calls into secur3=
2, which suggests that it is doing interpretive access control. It finds th=
e service's SID instead of the users SID in some slot in the token that it =
gets via RPC, and then everything goes downhill from there.Why VS feels the=
 need to put the PDB access in a separate process under separate access rig=
hts is very puzzling, but there it is.
"
=20
=20
Bug in Cygwin sshd?
=20
=20
 - Jay
=20

--
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