From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 88611 invoked by alias); 1 Apr 2015 13:33:05 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 88598 invoked by uid 89); 1 Apr 2015 13:33:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_FROM_URIBL_PCCC,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-ie0-f170.google.com Received: from mail-ie0-f170.google.com (HELO mail-ie0-f170.google.com) (209.85.223.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 01 Apr 2015 13:33:03 +0000 Received: by iebmp1 with SMTP id mp1so35606429ieb.0 for ; Wed, 01 Apr 2015 06:33:01 -0700 (PDT) X-Received: by 10.43.110.136 with SMTP id ek8mr76515406icc.87.1427895181334; Wed, 01 Apr 2015 06:33:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.116.21 with HTTP; Wed, 1 Apr 2015 06:32:21 -0700 (PDT) In-Reply-To: References: <551A13D8.1030701@cs.umass.edu> <20150331101534.GE32403@calimero.vinschen.de> <551A9149.4020408@cs.umass.edu> <1837571490.20150331235503@yandex.ru> <551B3EA8.4050607@cs.umass.edu> <392349513.20150401035240@yandex.ru> <20150401073824.GB493@calimero.vinschen.de> <18010304924.20150401153744@yandex.ru> From: Kal Sze Date: Wed, 01 Apr 2015 13:33:00 -0000 Message-ID: Subject: Re: OpenSSH 6.8p1-1 and keychain: can't determine fingerprint To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-04/txt/msg00022.txt.bz2 On 1 April 2015 at 21:03, wilson wrote: > > I saw the following on https://www.cygwin.com/ml/cygwin/2015-03/msg00477.= html and I've been having the same issue with keychain. The fix to the /usr= /bin/keychain shell script worked as shown, but I've added information abou= t where the fix belongs (in the script) later in this message. I suggest co= rrecting the indentations for the proposed fix as needed. > >> After updating to OpenSSH 6.8p1-1, I experienced an issue where, at ever= y login, keychain (in my .bash_profile) wrote a warning: >> >> >> The warning: >> Can't determine fingerprint from the following line, falling back to fil= ename >> >> A post (http://newscentral.exsees.com/item/d00c4734c9eed7abe32de6a741f5a= 3fe-8dd4abc7f69143e4ea63672f83a77a14 [1]) to an Arch Linux forum expressed = a similar report, along with a solution, adding a case for SHA256 or MD5: h= ttps://github.com/funtoo/keychain/blob/master/keychain.sh#L692 [2]. >> >> For clarity, that's: >> * SHA256:[0-9a-zA-Z+/=3D]*|* MD5:[0-9a-zA-Z+/=3D]*) >> # The new OpenSSH 6.8+ format, >> # 1024 SHA256:mVPwvezndPv/ARoIadVY98vAC0g+P/5633yTC4d/wXE /home/barn= ey/.ssh/id_dsa (DSA) >> echo "$ef_line" | cut -f2 -d' ' >> ;; >> >> I applied the changes to my /usr/bin/keychain, and the errors stopped. I= think this change belongs in Cygwin, too, since OpenSSH 6.8p1-1. > > > I applied this fix to the case statement (penultimate entry) in the extra= ct_fingerprints() function (around line 800) and it does seem to work for m= e as well. I would recommend this be added as a permanent fix in Cygwin's p= ackage. > > > -- > 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 > If you don't have to support multiple users (like me), just downloading the 2.8.0 keychain script to your local path and sourcing that that in .profile/.bash_profile is probably cleaner. I seem to notice that keychain 2.8.0 is slower to load than 2.7.1 though. -- 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