| From: | Sven <svoop_6cedifwf9e(at)delirium(dot)ch> |
|---|---|
| To: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: SSH tunnel key exchange methods |
| Date: | 2015-11-27 09:23:42 |
| Message-ID: | loom.20151127T101921-647@post.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers pgadmin-support |
> 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]
Any news on this? If there's no easy way to add safer kexes, I suggest
you disable the SSH feature altogether. SHA1 is dead and IMO nobody
should trust a connection established with SHA1 kexes in order to talk
to databases.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2015-11-27 09:31:43 | Re: SSH tunnel key exchange methods |
| Previous Message | Ashesh Vashi | 2015-11-23 08:30:35 | pgAdmin 4 commit: Added new url rules for each node by change NodeView |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2015-11-27 09:31:43 | Re: SSH tunnel key exchange methods |
| Previous Message | Nikolai Zhubr | 2015-11-27 09:12:21 | Re: Setof-returning function create script bug |