X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 19 Oct 2011 16:45:14 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: A quick question regarding a recent commit
Message-ID: <20111019144514.GA16351@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5D5CAD1E-BB44-4A1D-AA1A-1356448A6A5A AT linux-depot DOT com> <2glt97dmt8q6sct9ahgg3pp7m3codvronc AT 4ax DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <2glt97dmt8q6sct9ahgg3pp7m3codvronc@4ax.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Oct 19 09:58, Andrew Schulman wrote:
> > You recently applied a patch to the Cygwin tree regarding Windows
> > permissions when logging in via SSH with PubKey authentication (see
> > the link below). Another user in the thread confirmed it worked in
> > the latest snapshot. I download the latest cygwin-inst tar ball and
> > replaced the existing installed files on a machine that is suffering
> > from the same issue (with the ones from the archive). After rebooting
> > the machine the issue still persisted though :-( (trying to install
> > an MSI as administrator, works with password auth, not with pub key).
> 
> Please log in with pubkey and run 
> 
>   /cygdrive/c/Windows/System32/whoami /all
> 
> Then post the results here.  That will show which privileges your account
> has, and whether they're enabled.

This is probably not the same problem.  The solution for these cases is
either to just stick to password auth, or to use the passwordless setuid
methods 2 or 3 as outlined in
http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview
This should fix this kind of problem, especially method 3.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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