public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hiroyuki Kurokawa <kurokawh@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Every time I run ssh, ssh prompts "password:" with latest OpenSSH package.
Date: Thu, 03 Sep 2015 05:57:00 -0000	[thread overview]
Message-ID: <CABs5vS5ipP2R1ZHM8=5RC4Gv7Bww+c3-_8ng9tUvd9AswXzgLA@mail.gmail.com> (raw)
In-Reply-To: <833769153.20150903064857@yandex.ru>

Hi Andrey,

> This is not the right solution. Right solution would be to change your keys.
> While DSA keys aren't inherently insecure (quite opposite), FIPS compliant
> systems enforce DSA key length to 1024 bits, which is considered to be weak
> nowadays. You CAN use longer DSA keys, but not all systems support it.

I created a new 2048-bit RSA key and confirmed that ssh works fine with
this key & latest OpenSSH package without PubkeyAcceptedKeyTypes configuration.

Thanks,
Hiroyuki Kurokawa


2015-09-03 12:48 GMT+09:00 Andrey Repin <anrdaemon@yandex.ru>:
> Greetings, Hiroyuki Kurokawa!
>
>> Thanks Andrey for reply to my question.
>
>> George gave me an advice by a direct mail.
>> And his instruction solve my problem.
>
>>> If you use dsa key type, you need to add to your ssh client configuration file, either ~/.ssh/config or /etc/ssh_config, the following parameter:
>>>
>>> PubkeyAcceptedKeyTypes +ssh-dss
>>>
>>> If you use some other key type, then 'ssh -Q key' will list all supported key types, pick the right one and put it into config file instead of ssh-dss.
>>>
>>> I had the same problem after the last ssh upgrade.
>
>> Now the latest ssh works fine with ~/.ssh/config which contains
>> "PubkeyAcceptedKeyTypes +ssh-dss" because a type of my key is DSA.
>
>> I appreciate George so much.
>
> This is not the right solution. Right solution would be to change your keys.
> While DSA keys aren't inherently insecure (quite opposite), FIPS compliant
> systems enforce DSA key length to 1024 bits, which is considered to be weak
> nowadays. You CAN use longer DSA keys, but not all systems support it.
>
>
> --
> With best regards,
> Andrey Repin
> Thursday, September 3, 2015 06:46:29
>
> Sorry for my terrible english...
>



-- 
黒川裕之
kurokawh@gmail.com

--
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-09-03  5:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 13:58 Hiroyuki Kurokawa
2015-09-02 16:50 ` Andrey Repin
2015-09-03  3:25   ` Hiroyuki Kurokawa
2015-09-03  3:50     ` Andrey Repin
2015-09-03  5:57       ` Hiroyuki Kurokawa [this message]
2015-09-08 19:44       ` Andrew DeFaria

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='CABs5vS5ipP2R1ZHM8=5RC4Gv7Bww+c3-_8ng9tUvd9AswXzgLA@mail.gmail.com' \
    --to=kurokawh@gmail.com \
    --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).