X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:date:message-id:subject:from:to :content-type; q=dns; s=default; b=uO606zpMo+uR0FzfSJbrCdXSUQDQQ Q9OXJ3n2U6z7FF4n9BwYzuDu0EStcz05riNnpHmrVmiTNvFxlKBvfFXpAYnvi9IS NqtP7Ih7C9vy39PUYPr49SK7njzUShwpNlFZUJpV0US8WdSG9cnJzsv8YeZRNTbd 7bH6L9gT97RTXw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:date:message-id:subject:from:to :content-type; s=default; bh=u7WtuIyYONLDQXYiYxLtFwiLTVs=; b=Fvk t7PU/jWppqGgrd5aA2PCgswzTuC/fozueAHxPD/79t3nGjJMWT+e6lDN3gpKXbJx +FNHLUfqRC5Lm+arz9y4uVODcp/uBPGtWpi05KZEeaYIWQqQI5obYtVqyM+Kwkro Ui1hi+6Kg9amk4sZG/+kSrP9hmhGBDOzKqjk70nM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-oi0-f51.google.com MIME-Version: 1.0 X-Received: by 10.60.58.41 with SMTP id n9mr50898722oeq.73.1406045433660; Tue, 22 Jul 2014 09:10:33 -0700 (PDT) Date: Tue, 22 Jul 2014 18:10:33 +0200 Message-ID: Subject: cygwin ssh, sspi, gssapi From: Thomas Schweikle To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Hi! After looking arround for informations about cygwin supporting Windows SSPI interface I found various informations telling it does, but a lot of others stating it does not. Now I am a but confused. Does cygwin support SSPI directly? Does it support SSPI via external libraries -- some say I have to install heimdal (http://computing.help.inf.ed.ac.uk/kerberos-windows) for 64-bit Windows, then Identity-Manager from (https://www.secure-endpoints.com/netidmgr/v2//) to have ssh use Windows build in kerberos support. With Identity-Manager I can now watch the tickets I have, but -- ssh from cygwin states it could not find any ticket connecting to an kerberos enabled ssh-server. From Linux this works seamlessly. On Windows I can connect, but I have to enter my password again :-( debug3: preferred gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information No Kerberos credentials available debug1: Unspecified GSS failure. Minor code may provide more information No Kerberos credentials available debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information No Kerberos credentials available debug2: we did not send a packet, disable method The heimdal packages available for 64-bit cygwin seem not to have klist and friends available, but the libraries. SSH seems to use them, but do these libraries connect to SSPI or do they depend on some other infrastructure? If one could shed some light on this I'd be really happy! -- Thomas -- 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