211226 Michael wrote:
> On Sun, 26 Dec 2021 11:42:41 -0500, Philip Webb wrote:
>> I want to login to a remote site using 'ssh'.
>> The response I get is "Unable to negotiate with port
>> : no matching host key type found. Their offer: ssh-rsa,ssh-dss".
>> Yesterday, I updated 'openssh' :
> It
On Sun, 26 Dec 2021 18:07:56 +, Michael wrote:
> > Host a..cc
> > Ciphers +ssh-rsa
>
> The initial error is about "no matching host key type", so the option
> needed would be:
>
> HostKeyAlgorithms +ssh-rsa
You're right, I was looking at the wrong file when I looked for
On 12/26/21 9:42 AM, Philip Webb wrote:
I want to login to a remote site using 'ssh'.
The response I get is "Unable to negotiate with port :
no matching host key type found. Their offer: ssh-rsa,ssh-dss".
Yesterday, I updated 'openssh' :
Michael's pointing in the proper direction.
Check out
On Sunday, 26 December 2021 17:00:46 GMT Neil Bothwick wrote:
> On Sun, 26 Dec 2021 11:42:41 -0500, Philip Webb wrote:
> > I want to login to a remote site using 'ssh'.
> > The response I get is "Unable to negotiate with port
> > : no matching host key type found. Their offer: ssh-rsa,ssh-dss".
On Sun, 26 Dec 2021 11:42:41 -0500, Philip Webb wrote:
> I want to login to a remote site using 'ssh'.
> The response I get is "Unable to negotiate with port
> : no matching host key type found. Their offer: ssh-rsa,ssh-dss".
> Yesterday, I updated 'openssh' :
It sounds like the host may be
On Sun, 2021-12-26 at 11:42 -0500, Philip Webb wrote:
> I want to login to a remote site using 'ssh'.
> The response I get is "Unable to negotiate with port
> :
> no matching host key type found. Their offer: ssh-rsa,ssh-dss".
> Yesterday, I updated 'openssh' :
>
> Installed versions:
On Tuesday, 12 March 2019 15:12:46 GMT Neil Bothwick wrote:
> On 12 March 2019 15:10:24 GMT, Philip Webb wrote:
> >190312 Philip Webb wrote:
> >> Progress, but still a puzzle. I commented the lines in /etc/...
> >> & when I use the IP, not the URL, the connection goes thro' ;
Good, we're
On 12 March 2019 15:10:24 GMT, Philip Webb wrote:
>190312 Philip Webb wrote:
>> Progress, but still a puzzle. I commented the lines in /etc/...
>> & when I use the IP, not the URL, the connection goes thro' ;
>> when I use the URL, it still doesn't. Here's the output :
> ... skip ...
>> So
190312 Philip Webb wrote:
> Progress, but still a puzzle. I commented the lines in /etc/...
> & when I use the IP, not the URL, the connection goes thro' ;
> when I use the URL, it still doesn't. Here's the output :
... skip ...
> So why does IP vs URL make a difference ??
Thanks to Nuno
190312 Mick wrote:
> On Tuesday, 12 March 2019 10:02:07 GMT Philip Webb wrote:
>> I tried adding the 'Ciphers' line, which is mentioned in the I/net page,
>> but Ssh chokes, so I commented it again :
> The ciphers do not come into play
> until the key exchange algos have been agreed upon.
> In
Hi Philip,
On Tuesday, 12 March 2019 10:02:07 GMT Philip Webb wrote:
> 190311 Neil Bothwick wrote:
> > Do you have any other Host stanzas in the config?
>
> No : /etc/ssh/ssh_config has the following uncommented lines :
>
> # Send locale environment variables. #367017
> SendEnv LANG
190311 Neil Bothwick wrote:
> Do you have any other Host stanzas in the config?
No : /etc/ssh/ssh_config has the following uncommented lines :
# Send locale environment variables. #367017
SendEnv LANG LC_ALL LC_COLLATE LC_CTYPE LC_MESSAGES LC_MONETARY LC_NUMERIC
LC_TIME LANGUAGE
On Mon, 11 Mar 2019 21:35:54 +, Mick wrote:
> > > > It shows that ssh is reading your config file, but not picking up
> > > > the options for this host. I would expect to see something like
> > > >
> > > > debug1: Reading configuration data /home/nelz/.config/ssh
> > > > debug1:
On Monday, 11 March 2019 17:34:20 GMT Neil Bothwick wrote:
> On Mon, 11 Mar 2019 16:06:59 +, Mick wrote:
> > > It shows that ssh is reading your config file, but not picking up the
> > > options for this host. I would expect to see something like
> > >
> > > debug1: Reading configuration data
On Mon, 11 Mar 2019 16:06:59 +, Mick wrote:
> > It shows that ssh is reading your config file, but not picking up the
> > options for this host. I would expect to see something like
> >
> > debug1: Reading configuration data /home/nelz/.config/ssh
> > debug1: /home/nelz/.config/ssh line N:
On Monday, 11 March 2019 13:42:14 GMT Neil Bothwick wrote:
> On Mon, 11 Mar 2019 09:08:14 -0400, Philip Webb wrote:
> > 190311 Neil Bothwick wrote:
> > > Have you run ssh with -v
> > > to see what configuration options it is reading from where.
> > > Bear in mind that ssh stops at the first
On Mon, 11 Mar 2019 09:08:14 -0400, Philip Webb wrote:
> 190311 Neil Bothwick wrote:
> > Have you run ssh with -v
> > to see what configuration options it is reading from where.
> > Bear in mind that ssh stops at the first matching host definition,
> > so if you have a "host *" in your config, it
190311 Neil Bothwick wrote:
> Have you run ssh with -v
> to see what configuration options it is reading from where.
> Bear in mind that ssh stops at the first matching host definition,
> so if you have a "host *" in your config, it must be last.
This is what I get :
522: ~> ssh -v
On Mon, 11 Mar 2019 05:23:36 -0400, Philip Webb wrote:
> 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.
>
>
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
>>
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
On Mon, 11 Mar 2019 08:43:52 +, Mick wrote:
> > 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
> >
On Monday, 11 March 2019 08:31:33 GMT Neil Bothwick wrote:
> On Mon, 11 Mar 2019 01:41:19 -0400, Philip Webb wrote:
> > 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
On Mon, 11 Mar 2019 01:41:19 -0400, Philip Webb wrote:
> 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
On Monday, 11 March 2019 05:41:19 GMT Philip Webb wrote:
[snip ...]
> 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
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:
>>
Hi Philip,
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
The nc command does nothing when run from the same host I'm trying to
ssh in to.
Ok so you may not have an ssh problem (so ignore the ssh specific stuff for
now) you have a network problem. It will be either routing or firewalling.
If you can ping the box, then its a firewall problem. So, try
On Saturday 26 February 2011 07:49:44 Adam Carter wrote:
The nc command does nothing when run from the same host I'm trying to
ssh in to.
Ok so you may not have an ssh problem (so ignore the ssh specific stuff for
now) you have a network problem. It will be either routing or firewalling.
On 02/26/2011 03:13 AM, Mick wrote:
On Saturday 26 February 2011 07:49:44 Adam Carter wrote:
The nc command does nothing when run from the same host I'm trying to
ssh in to.
Ok so you may not have an ssh problem (so ignore the ssh specific stuff for
now) you have a network problem. It will
When ssh'ing in from a remote updated Gentoo box the Read from socket
failed: Connection reset by peer message is displayed. This message is
not displayed when trying to ssh in from inside the network.
Ok that's different (and not consistent with the Connection timed out
message, but lets
Did you remember to restart the sshd on your amd64 system? If not, try
disabling the new high performance stuff on the client. I had a problem
logging into a solaris box until i disabled it. In my ~/.ssh/config file I
added;
host ip or hostname
HPNDisabled yes
On 02/24/2011 08:08 PM, dhk wrote:
On 02/24/2011 06:30 PM, Mick wrote:
On Thursday 24 February 2011 21:51:56 dhk wrote:
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
On 02/25/2011 05:36 AM, Adam Carter wrote:
Did you remember to restart the sshd on your amd64 system? If not, try
disabling the new high performance stuff on the client. I had a problem
logging into a solaris box until i disabled it. In my ~/.ssh/config file I
added;
host ip or hostname
dhk writes:
On 02/25/2011 05:36 AM, Adam Carter wrote:
Did you remember to restart the sshd on your amd64 system? If not, try
disabling the new high performance stuff on the client. I had a problem
logging into a solaris box until i disabled it. In my ~/.ssh/config
file I added;
On Friday 25 February 2011 12:09:38 dhk wrote:
On 02/24/2011 08:08 PM, dhk wrote:
On 02/24/2011 06:30 PM, Mick wrote:
On Thursday 24 February 2011 21:51:56 dhk wrote:
Thanks, but I've tried that. ssh'ing to the hostname and loopback
address work. However, when I go out to the WAN it
On Tue, Feb 22, 2011 at 6:43 AM, dhk dhk...@optonline.net 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?
Thanks
On 02/23/2011 03:42 AM, Joost Roeleveld wrote:
On Tuesday 22 February 2011 14:51:31 Mick wrote:
On 22 February 2011 14:19, dhk...@optonline.net wrote:
- Original Message -
From: Mick
There was a change in the default ssh encryption algorithm. You may
want to check if that is
On 24 February 2011 13:17, dhk dhk...@optonline.net wrote:
On 02/23/2011 03:42 AM, Joost Roeleveld wrote:
On Tuesday 22 February 2011 14:51:31 Mick wrote:
On 22 February 2011 14:19, dhk...@optonline.net wrote:
- Original Message -
From: Mick
There was a change in the default ssh
On 02/24/2011 08:53 AM, Mick wrote:
On 24 February 2011 13:17, dhk dhk...@optonline.net wrote:
On 02/23/2011 03:42 AM, Joost Roeleveld wrote:
On Tuesday 22 February 2011 14:51:31 Mick wrote:
On 22 February 2011 14:19, dhk...@optonline.net wrote:
- Original Message -
From: Mick
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
On Thursday 24 February 2011 18:09:22 dhk wrote:
On 02/24/2011 08:53 AM, Mick wrote:
Have you tried using ssh user@host to login with?
At first all I did was an update: emerge -uDN world . They when it
didn't work I removed all public and private keys and restarted sshd.
That didn't
On Thursday 24 February 2011 21:51:56 dhk wrote:
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.
Just to state the
On 02/24/2011 06:30 PM, Mick wrote:
On Thursday 24 February 2011 21:51:56 dhk wrote:
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
On 25/2/2011, at 1:08am, dhk wrote:
I don't have the nc comand. What package is it in?
net-analyzer/netcat
On Tuesday 22 February 2011 14:51:31 Mick wrote:
On 22 February 2011 14:19, dhk...@optonline.net wrote:
- Original Message -
From: Mick
There was a change in the default ssh encryption algorithm. You may
want to check if that is causing the problem.
How would I do that?
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.
On 22 February 2011 13:24, dhk dhk...@optonline.net 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
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
- 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
On 22 February 2011 14:19, dhk...@optonline.net wrote:
- Original Message -
From: Mick
There was a change in the default ssh encryption algorithm. You may
want to check if that is causing the problem.
How would I do that?
By examining your config files? Previously your keys
Travis Osterman wrote:
On my recent gentoo install, I can't get past the password prompt when
trying to log into the box via ssh.
$ ssh [EMAIL PROTECTED] (password: and hangs)
$ ssh [EMAIL PROTECTED] bash --login --noprofile -i (works)
/var/log/messages
Jun 14 20:13:37 spot sshd[10366]:
On 6/15/05, Zac Medico [EMAIL PROTECTED] wrote:
Travis Osterman wrote:
On my recent gentoo install, I can't get past the password prompt when
trying to log into the box via ssh.
$ ssh [EMAIL PROTECTED] (password: and hangs)
$ ssh [EMAIL PROTECTED] bash --login --noprofile -i (works)
53 matches
Mail list logo
