Date: Sun, 7 Aug 2016 21:06:37 +0300 From: Andrey Chernov <ache@freebsd.org> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: Bruce Simpson <bms@fastmail.net>, Warner Losh <wlosh@bsdimp.com>, src-committers@freebsd.org, svn-src-all@freebsd.org, Oliver Pinter <oliver.pinter@hardenedbsd.org>, svn-src-head@freebsd.org, =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= <des@freebsd.org> Subject: Re: svn commit: r303716 - head/crypto/openssh Message-ID: <e43e43f2-4043-847f-f1d8-f791e2d8b91d@freebsd.org> In-Reply-To: <2dd7e952-ca28-57cb-ac8a-39d895b51d06@freebsd.org> References: <9a01870a-d99d-13a2-54bd-01d32616263c@fastmail.net> <CAPQ4fftQ30_aqU8V_ea-WEKBdMZs5H9Rwxnfa0crid_df049nQ@mail.gmail.com> <b99c06ac-82d6-ccda-419c-2ece5be4636f@fastmail.net> <30e655d1-1df7-5e2a-fccb-269e3cea4684@freebsd.org> <20160807125227.GC22212@zxy.spb.ru> <7237f5e6-fd65-a7e5-7751-4ed1c464b39a@freebsd.org> <4D28752C-0584-4294-9250-FA88B0C6E805@bsdimp.com> <c54673d0-8edd-b185-c86e-95a6aa6d0846@fastmail.net> <32b82f9f-7f78-6358-030a-90aed54bb8a8@freebsd.org> <0740b662-4a36-f834-229a-d16a5a6dde14@freebsd.org> <20160807173734.GD22212@zxy.spb.ru> <2dd7e952-ca28-57cb-ac8a-39d895b51d06@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07.08.2016 20:43, Andrey Chernov wrote: > On 07.08.2016 20:37, Slawa Olhovchenkov wrote: >> On Sun, Aug 07, 2016 at 08:34:55PM +0300, Andrey Chernov wrote: >> >>> On 07.08.2016 20:31, Andrey Chernov wrote: >>>> On 07.08.2016 19:14, Bruce Simpson wrote: >>>>> On 07/08/16 15:40, Warner Losh wrote: >>>>>> That’s a cop-out answer. We, as a project, need to articulate to our >>>>>> users, whom we care about, why this rather obnoxious hit to usability >>>>>> was taken. The answer must be more complete than “We just disabled >>>>>> it because upstream disabled it for reasons we’re too lazy to explain >>>>>> or document how to work around" >>>>> >>>>> Alcatel-Lucent OmniSwitch 6800 login broken (pfSense 2.3.2 which >>>>> accepted the upstream change, workaround no-go) >>>>> >>>>> [2.3.2-RELEASE][root@gw.lab]/root: ssh -l admin >>>>> -oKexAlgorithms=+diffie-hellman-group1-sha1 192.168.1.XXX >>>>> Fssh_ssh_dispatch_run_fatal: Connection to 192.168.1.XXX port 22: DH GEX >>>>> group out of range >>>>> >>>> >>>> DH prime size must be at least 2048, openssh now refuse lower values. >>>> Commonly used DH size 1024 can be easily broken. See https://weakdh.org >>>> >>> diffie-hellman-group1-sha1 use DH 1024 and insecure sha1 both. >> >> IMHO, this is wrong choise: totaly lost of control now vs teoretical >> compromise of control in the future. > > Please note that it was not my choice and I can't answer what to do with > non-upgradeable hardware question, address it to the author. I just tell > you _why_ it happens. > BTW, compromise is practical enough. From https://weakdh.org/ "A close reading of published NSA leaks shows that the agency's attacks on VPNs are consistent with having achieved such a break."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e43e43f2-4043-847f-f1d8-f791e2d8b91d>