public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: dhk <dhkuhl@optonline.net>
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ssh problem
Date: Thu, 24 Feb 2011 16:51:56 -0500	[thread overview]
Message-ID: <4D66D2FC.1010003@optonline.net> (raw)
In-Reply-To: <201102241201.12178.matt@deploylinux.net>

On 02/24/2011 03:01 PM, Matthew Marlowe wrote:
> On Thursday, February 24, 2011 10:09:22 am dhk wrote:
>>>>
>>>> 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.
>>>>
> 
> I encountered a similar, if not the same, problem this morning.
> Upgraded SSH, rebooted server, and no longer able to login.  Logs showed 
> errors I had not seen before.
> 
> I managed to solve the problem when I noticed that ssh'ing to the fqdn of the 
> server failed, but ssh'ing to the server hostname worked.  This implied there 
> might be an issue with the known_hosts file, so I blew away that on both the 
> client and server and all was well.
> 
> I'm guessing the upgrade modified the default ssh host keys, the new code 
> somehow doesn't give the normal error about discrepencies in known_hosts, and 
> consequently although ones user keys are still fine, it fails.  The issue here 
> is really the new error isn't nearly as understandable as the old.
> 
> Anyhow, try it and I hope it works.
> 
> Matt

Thanks, but I've tried that.  ssh'ing to the hostname and loopback
address work.  However, when I go out to the WAN it doesn't.  So I can't
ssh user@123.123.123.123 even though I have port 22 open on the switch
for my ip.



  parent reply	other threads:[~2011-02-24 22:07 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
     [not found]                   ` <201102241201.12178.matt@deploylinux.net>
2011-02-24 21:51                     ` dhk [this message]
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=4D66D2FC.1010003@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