From: dhkuhl@optonline.net
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ssh problem
Date: Tue, 22 Feb 2011 14:19:19 +0000 (GMT) [thread overview]
Message-ID: <e656eb08a5ec.4d63c5e7@optonline.net> (raw)
In-Reply-To: <AANLkTiksxf2Gp5sxA8WZBkM-Lp-qJ6ak1N-JBchz8ya7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
----- Original Message -----From: Mick Date: Tuesday, February 22, 2011 9:11 amSubject: Re: [gentoo-user] ssh problemTo: gentoo-user@lists.gentoo.org> On 22 February 2011 13:24, dhk wrote:> > On 02/22/2011 07:37 AM, Alan McKinnon wrote:> >> On Tuesday 22 February 2011 06:43:33 dhk wrote:> >>> After a recent upgrade to ssh I can no longer log into my > Gentoo box> >>> (amd64) from another Gentoo box (x86) that has also had a > recent upgrade> >>> to ssh. However, I can log in to it from Suse and Redhat boxes.> >>>> >>> Any ideas?> >>> >> None whatsoever.> >>> >> Supplying logs might change that though.> >>> >>> >> > I don't see anything in the logs, but with the -v command I > get the> > following when trying to log in through the WAN. Also port 22 > is open> > on the switch.> >> >> > $ ssh -v -v -v user@12.12.12.123> > OpenSSH_5.8p1-hpn13v10, OpenSSL 1.0.0d 8 Feb 2011> > debug1: Reading configuration data /etc/ssh/ssh_config> > debug2: ssh_connect: needpriv 0> > debug1: Connecting to 12.12.12.123 [12.12.12.123] port 22.> > There was a change in the default ssh encryption algorithm. You may> want to check if that is causing the problem.> -- > Regards,> Mick> >How would I do that?
[-- Attachment #2: Type: text/html, Size: 1780 bytes --]
next prev parent reply other threads:[~2011-02-22 15:04 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 [this message]
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
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=e656eb08a5ec.4d63c5e7@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