X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 16 Nov 2009 09:38:44 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: subinacl not consistent with getfacl under ssh login (USERNAME=SYSTEM) Message-ID: <20091116083844.GB3503@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <26355883 DOT post AT talk DOT nabble DOT com> <26366622 DOT post AT talk DOT nabble DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26366622.post@talk.nabble.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Nov 15 20:02, aputerguy wrote: > > OK - I just re-read the ntsec portion of the cygwin manual and found this > paragraph: > > [...] > > So is 'subinacl' just another example of these badly behaved non-Cygwin > applications? > If so, is there anything one can do other than to use one of the other > methods to get a properly authenticated ssh login? The other methods *are* the solutions for this problem. 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