From: Philip Webb <purslow@ca.inter.net>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Ssh problem
Date: Sun, 10 Mar 2019 03:25:54 -0400 [thread overview]
Message-ID: <20190310072554.GD1945@ca.inter.net> (raw)
I updated Ssh yesterday :
net-misc/openssh
Available versions: 7.5_p1-r4 7.7_p1-r9^t 7.9_p1-r4^t {X X509 audit bindist debug (+)hpn kerberos ldap ldns libedit libressl livecd pam +pie sctp selinux skey ssh1 +ssl static test ABI_MIPS="n32" KERNEL="linux"}
Installed versions: 7.9_p1-r4^t([2019-03-09 22:25:11])(X ssl -X509 -audit -bindist -debug -hpn -kerberos -ldns -libedit -libressl -livecd -pam -pie -sctp -selinux -static -test ABI_MIPS="-n32" KERNEL="linux")
Previously, I was using : net-misc/openssh-7.7_p1-r9 .
Today, I tried to access an off-site via Ssh ,
which I've been doing for years & got this :
ssh x.y.z
Unable to negotiate with 128.100.160.1 port 22: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
'x.y.z' disguises the site's URL, which doesn't seem to be a problem.
Can anyone suggest what's gone wrong ?
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next reply other threads:[~2019-03-10 7:26 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 7:25 Philip Webb [this message]
2019-03-10 8:23 ` [gentoo-user] Re: Ssh problem Nikos Chantziaras
2019-03-10 10:31 ` [gentoo-user] " Nils Freydank
2019-03-11 5:41 ` [gentoo-user] Ssh problem : half-solved Philip Webb
2019-03-11 8:30 ` Mick
2019-03-11 8:31 ` Neil Bothwick
2019-03-11 8:43 ` Mick
2019-03-11 9:08 ` Neil Bothwick
2019-03-11 9:23 ` Philip Webb
2019-03-11 9:30 ` Bill Kenworthy
2019-03-11 10:00 ` Neil Bothwick
2019-03-11 13:08 ` Philip Webb
2019-03-11 13:42 ` Neil Bothwick
2019-03-11 16:06 ` Mick
2019-03-11 17:34 ` Neil Bothwick
2019-03-11 21:35 ` Mick
2019-03-11 22:14 ` Neil Bothwick
2019-03-12 10:02 ` Philip Webb
2019-03-12 10:49 ` Mick
2019-03-12 14:32 ` Philip Webb
2019-03-12 15:10 ` [gentoo-user] Ssh problem : solved but weird Philip Webb
2019-03-12 15:12 ` Neil Bothwick
2019-03-12 16:59 ` Mick
2019-03-12 14:46 ` [gentoo-user] Re: Ssh problem : half-solved Nuno Silva
-- strict thread matches above, loose matches on Subject: below --
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
2011-02-22 11:43 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
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
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=20190310072554.GD1945@ca.inter.net \
--to=purslow@ca.inter.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