On Fri, Nov 27, 2015 at 9:23 AM, Sven <svoop_6cedifw...@delirium.ch> wrote: >> 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.
Akshay, you know that code best of all. How do we enable safer kexes? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
