From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ssh problem : half-solved
Date: Mon, 11 Mar 2019 17:30:35 +0800 [thread overview]
Message-ID: <994d6ba7-c001-57a7-0e4d-7ca145da6584@iinet.net.au> (raw)
In-Reply-To: <20190311092336.GB1934@ca.inter.net>
On 11/3/19 5:23 pm, Philip Webb wrote:
> 190311 Neil Bothwick + Mick wrote:
> NB> Try without the +, that works for me here. I have an appliance
>> that uses outdated algorithms and this config works for me
>> Host 1.2.3.4
>> Ciphers 3des-cbc
>> KexAlgorithms diffie-hellman-group1-sha1
>> HostKeyAlgorithms ssh-dss
> I tried adding the 2 extra lines to ~/.ssh/config , but no joy.
> I didn't reboot, but it's not clear that that would make any difference.
>
> M> As I understand it the "+" merely adds one more cipher to the collection.
>> This is probably safer. If the server has been updated
>> and non-legacy key exchange algorithms are now available they can be used.
>> Without "+" the directive for the client is exclusive :
>> only use this algorithm and nothing else.
> That's what the 'man' says.
>
> NB> That's how I read it, but it says it appends to the list,
>> so this is the last option tried,
>> while an earlier one could possibly be triggering the failure.
>> With + would be better, but it would be worth trying without.
> I tried both & neither gets Ssh to recognise the config.
>
> This is a puzzle : are they any other suggestions ?
>
This works for me (ancient Cisco ...)
rattus ~ # cat ~/.ssh/config
Host 192.168.44.1
KexAlgorithms +diffie-hellman-group1-sha1
Host ghost
KexAlgorithms +diffie-hellman-group1-sha1
Which file are putting it in? - this is the client side user.
next prev parent reply other threads:[~2019-03-11 9:30 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 ` [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 [this message]
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=994d6ba7-c001-57a7-0e4d-7ca145da6584@iinet.net.au \
--to=billk@iinet.net.au \
--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