From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Sven <svoop_6cedifwf9e(at)delirium(dot)ch> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org>, Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
Subject: | Re: SSH tunnel key exchange methods |
Date: | 2015-11-10 10:11:00 |
Message-ID: | CA+OCxoxn9LWXPR=DQi0gnAkur+ZQch37OB8iH+0e7fGRH8-U=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Akshay;
Is this something that's fixable in our code, or do we need to update
libssh2, or...?
On Tue, Nov 10, 2015 at 8:39 AM, Sven <svoop_6cedifwf9e(at)delirium(dot)ch> wrote:
> Hi
>
> The key exchange methods offered when opening an SSH tunnel are all
> SHA1 and therefore too weak:
>
> [sshd] fatal: Unable to negotiate with xxx.xxx.xxx.xxx: no matching
> key exchange method found. Their offer:
> diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,
> diffie-hellman-group1-sha1 [preauth]
>
> Is it possible to update pgadmin for safer kexes? IMHO, at least
> diffie-hellman-group-exchange-sha256 would be nice, better even
> curve25519-sha256(at)libssh(dot)org as well.
>
> Thanks for considering this!
>
>
>
> --
> Sent via pgadmin-support mailing list (pgadmin-support(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-support
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Grinko | 2015-11-10 15:13:20 | The underscore and the height of rows in the grid results |
Previous Message | Sven | 2015-11-10 08:39:59 | SSH tunnel key exchange methods |