X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: From: Jay K To: cygwin Subject: RE: running MS link.exe under Cygwin sshd? Date: Mon, 3 Aug 2009 04:11:31 +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 List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com I found that Interix sshd and WinSSHD work ok here. So it is something specific to Cygwin. =20 - Jay ---------------------------------------- > From: jay.krell@cornell.edu > To: cygwin@cygwin.com > Subject: running MS link.exe under Cygwin sshd? > Date: Sat, 1 Aug 2009 04:50:15 +0000 > > > http://social.msdn.microsoft.com/forums/en-US/vcgeneral/thread/eb49be0b-2= a8c-4d55-8791-17e3cb1364c1 > > " > This issue is caused because cygwin does not implement a full login proce= ss. It tries to impersonate, but it looks to me as if it does not make the = necessary 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 secu= r32, which suggests that it is doing interpretive access control. It finds = the service's SID instead of the users SID in some slot in the token that i= t gets via RPC, and then everything goes downhill from there.Why VS feels t= he need to put the PDB access in a separate process under separate access r= ights is very puzzling, but there it is. > " > > > Bug in Cygwin sshd? > > > - Jay > -- 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