public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: wilson <wilson@ds.net>
To: cygwin@cygwin.com
Subject: Re: OpenSSH 6.8p1-1 and keychain: can't determine fingerprint
Date: Wed, 01 Apr 2015 13:27:00 -0000	[thread overview]
Message-ID: <cd3389f79bfccaeb880197f4534950f5@www.ds.net> (raw)
In-Reply-To: <18010304924.20150401153744@yandex.ru>

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 about where the 
fix belongs (in the script) later in this message. I suggest correcting 
the indentations for the proposed fix as needed.

> After updating to OpenSSH 6.8p1-1, I experienced an issue where, at 
> every login, keychain (in my .bash_profile) wrote a warning:
> 
> <snip>
> The warning:
> Can't determine fingerprint from the following line, falling back to 
> filename
> 
> A post 
> (http://newscentral.exsees.com/item/d00c4734c9eed7abe32de6a741f5a3fe-8dd4abc7f69143e4ea63672f83a77a14 
> [1]) to an Arch Linux forum expressed a similar report, along with a 
> solution, adding a case for SHA256 or MD5: 
> https://github.com/funtoo/keychain/blob/master/keychain.sh#L692 [2].
> 
> For clarity, that's:
> * SHA256:[0-9a-zA-Z+/=]*|* MD5:[0-9a-zA-Z+/=]*)
>     # The new OpenSSH 6.8+ format,
>     # 1024 SHA256:mVPwvezndPv/ARoIadVY98vAC0g+P/5633yTC4d/wXE 
> /home/barney/.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 
extract_fingerprints() function (around line 800) and it does seem to 
work for me as well. I would recommend this be added as a permanent fix 
in Cygwin's package.

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

  reply	other threads:[~2015-04-01 13:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31  4:11 More about permissions Eliot Moss
2015-03-31 10:18 ` Corinna Vinschen
2015-03-31 12:22   ` Eliot Moss
2015-03-31 15:14     ` Corinna Vinschen
     [not found]     ` <1837571490.20150331235503@yandex.ru>
2015-04-01  0:41       ` Eliot Moss
2015-04-01  1:05         ` Andrey Repin
2015-04-01  7:38           ` Corinna Vinschen
2015-04-01 12:50             ` Andrey Repin
2015-04-01 13:27               ` wilson [this message]
2015-04-01 13:33                 ` OpenSSH 6.8p1-1 and keychain: can't determine fingerprint Kal Sze
2015-04-01 17:45             ` More about permissions Eliot Moss
2015-04-01  7:35         ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2015-03-27  5:04 OpenSSH 6.8p1-1 and keychain: can't determine fingerprint White, W John (GE Transportation)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cd3389f79bfccaeb880197f4534950f5@www.ds.net \
    --to=wilson@ds.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).