X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 10 Oct 2008 11:36:20 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: ssh accepting AD kerberos tickets Message-ID: <20081010093620.GH9289@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <48EE2C2A DOT 4090004 AT liddicott DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48EE2C2A.4090004@liddicott.com> User-Agent: Mutt/1.5.16 (2007-06-09) 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 Oct 9 17:07, Sam Liddicott wrote: > I've read about cygwin, ssh and network access till my neck hurts. > > It seems to me that if someone :-) integrates ssh kerberos > authentication such that sshd accepts an AD kerberos ticket, that > _maybe_ this could be associated with the login and give the client > session the right credentials to use the network. > > Is this true? That should automatically work that way by using password auth. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/