public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: dhk <dhkuhl@optonline.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ssh problem
Date: Thu, 24 Feb 2011 13:09:22 -0500	[thread overview]
Message-ID: <4D669ED2.2060108@optonline.net> (raw)
In-Reply-To: <AANLkTi=yg5GD8m5RcZDADLrjuxD9Aedt5Aogg6bo1GB2@mail.gmail.com>

On 02/24/2011 08:53 AM, Mick wrote:
> On 24 February 2011 13:17, dhk <dhkuhl@optonline.net> wrote:
>> On 02/23/2011 03:42 AM, Joost Roeleveld wrote:
>>> On Tuesday 22 February 2011 14:51:31 Mick wrote:
>>>> On 22 February 2011 14:19,  <dhkuhl@optonline.net> wrote:
>>>>> ----- Original Message -----
>>>>> From: Mick
>>>>>
>>>>>> There was a change in the default ssh encryption algorithm. You may
>>>>>> want to check if that is causing the problem.
>>>>>
>>>>> How would I do that?
>>>>
>>>> By examining your config files?  Previously your keys would be in
>>>> ~/.ssh/id_dsa[rsa].pub, but now with ECDSA being the default they
>>>> would be in ~/.ssh/id_ecdsa.pub
>>>>
>>>> I recall something being mentioned in the elog asking to regenerate
>>>> the key-pair.
>>>>
>>>> HTH.
>>>
>>> If this is the case, you could try speciying your key on the command-line
>>> using the "-i" flag:
>>>
>>> # ssh -i .ssh/id_dsa.pub <host....>
>>>
>>> Replace the file with the one on your machine.
>>>
>>> HTH,
>>>
>>> Joost
>>>
>>>
>>
>> I still haven't gotten this to work.  Am I the only one using this?  The
>> "ssh -i .ssh/id_dsa.pub host" didn't work.  I get a message "Read from
>> socket failed: Connection reset by peer" with or without the -i option.
>>
>> When I re-emerged openssh the following output is displayed.
>>
>> # emerge openssh
>> Calculating dependencies... done!
>>>>> Verifying ebuild manifests
>>>>> Emerging (1 of 1) net-misc/openssh-5.8_p1-r1
>>>>> Installing (1 of 1) net-misc/openssh-5.8_p1-r1
>>>>> Jobs: 1 of 1 complete                           Load avg: 2.80,
>> 1.95, 1.43
>>
>>  * Messages for package net-misc/openssh-5.8_p1-r1:
>>
>>  * Starting with openssh-5.8p1, the server will default to a newer key
>>  * algorithm (ECDSA).  You are encouraged to manually update your stored
>>  * keys list as servers update theirs.  See ssh-keyscan(1) for more info.
>>  * Remember to merge your config files in /etc/ssh/ and then
>>  * reload sshd: '/etc/init.d/sshd reload'.
>>  * Please be aware users need a valid shell in /etc/passwd
>>  * in order to be allowed to login.
>>>>> Auto-cleaning packages...
>>
>>>>> No outdated packages were found on your system.
>>
>>  * GNU info directory index is up-to-date.
>>
>> The ssh-keyscan man page hasn't helped.
>>
>> As of now I can only log in from older systems.
> 
> This would imply that your older (rsa/dsa) server keys still work.
> 
> What have you changed on your Gentoo client?
> 
> Have you tried using ssh user@host to login with?

At first all I did was an update:  emerge -uDN world .  They when it
didn't work I removed all public and private keys and restarted sshd.
That didn't work then I tried the ssh-keygen and ssh-keyscan.  That
didn't work so I removed all keys again and restarted sshd.  Are there
ssh_config or sshd_config options that should be set?

Thanks,

dhk



  reply	other threads:[~2011-02-24 18:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 11:43 [gentoo-user] ssh problem dhk
2011-02-22 12:37 ` Alan McKinnon
2011-02-22 13:24   ` dhk
2011-02-22 13:30     ` Mick
2011-02-22 14:19       ` dhkuhl
2011-02-22 14:51         ` Mick
2011-02-23  8:42           ` Joost Roeleveld
2011-02-24 13:17             ` dhk
2011-02-24 13:53               ` Mick
2011-02-24 18:09                 ` dhk [this message]
     [not found]                   ` <201102241201.12178.matt@deploylinux.net>
2011-02-24 21:51                     ` dhk
2011-02-24 23:30                       ` Mick
2011-02-25  1:08                         ` dhk
2011-02-25  2:30                           ` Stroller
2011-02-25 12:09                           ` dhk
2011-02-25 23:08                             ` Mick
2011-02-26  7:49                             ` Adam Carter
2011-02-26  8:13                               ` Mick
2011-02-26 11:05                                 ` dhk
2011-02-26 13:23                                   ` Adam Carter
2011-02-24 23:26                   ` Mick
2011-02-25 10:36 ` Adam Carter
2011-02-25 12:12   ` dhk
2011-02-25 12:45     ` Alex Schuster
2011-02-26  0:09 ` Mark Shields
  -- strict thread matches above, loose matches on Subject: below --
2019-03-10  7:25 [gentoo-user] Ssh problem Philip Webb
2019-03-10 10:31 ` Nils Freydank
2021-12-26 16:42 [gentoo-user] ssh problem Philip Webb
2021-12-26 16:55 ` Branko Grubić
2021-12-26 17:00 ` Neil Bothwick
2021-12-26 18:07   ` Michael
2021-12-26 20:11     ` Neil Bothwick
2021-12-27 11:03     ` Philip Webb
2021-12-26 19:20 ` Grant Taylor

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=4D669ED2.2060108@optonline.net \
    --to=dhkuhl@optonline.net \
    --cc=gentoo-user@lists.gentoo.org \
    /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