public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ssh problem : half-solved
Date: Mon, 11 Mar 2019 01:41:19 -0400	[thread overview]
Message-ID: <20190311054119.GA1934@ca.inter.net> (raw)
In-Reply-To: <10172104.eGJ9VJlZd9@pygoscelis>

190310 Nils Freydank wrote:
> Am Sonntag, 10. März 2019, 08:25:54 CET schrieb Philip Webb:
>> I updated Ssh yesterday :
>> [...]
>>   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
> ssh tells you straight forward what the issue is:
> Within the key exchange at the begin of the communication
> there was no way to establish a connection between server and client,
> probably because the client has a more secure setup than the server.
> This happens mostly due to old ssh versions serverside.

Yes, they mb a bit slow to upgrade.

> You can find solutions pretty fast
> by just searching for "Their offer: <key exchange offers>",
> e.g. https://unix.stackexchange.com/questions/340844/
> how-to-enable-diffie-hellman-group1-sha1-key-exchange-on-debian-8-0

That forum contains a solution :

  ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 123.123.123.123

That gets me thro' & I can do my work there.

> Enable legacy and possible less secure key exchange formats and ciphers
> only per server and not globally
> and if possible upgrade the SSH server version.

However, I've tried to insert an instruction in config files,
but nothing changes after a reboot.
I've tried adding to  ~/.ssh/config  &  /etc/ssh/ssh_config :

  Host 128.100.160.1
    KexAlgorithms +diffie-hellman-group1-sha1

That is what seems to be required by 'man 5 ssh_config'.

Can anyone suggest what + where to tell Ssh to do it every time ?

>> 'x.y.z' disguises the site's URL, which doesn't seem to be a problem.
> That is indeed perfectly fine;
> you might want to hide the IP address in the future as well ;-)

Indeed (red face) : it was at the end of my day.
No point in trying to hide it now (wry smile).

-- 
========================,,============================================
SUPPORT     ___________//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT    `-O----------O---'   purslowatchassdotutorontodotca



  reply	other threads:[~2019-03-11  5:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10  7:25 [gentoo-user] Ssh problem Philip Webb
2019-03-10  8:23 ` [gentoo-user] " Nikos Chantziaras
2019-03-10 10:31 ` [gentoo-user] " Nils Freydank
2019-03-11  5:41   ` Philip Webb [this message]
2019-03-11  8:30     ` [gentoo-user] Ssh problem : half-solved 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

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=20190311054119.GA1934@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