[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PATCH] Re: Logjam mitigation for Wheezy?



On Wednesday 03 June 2015 16:07:56, Thorsten Glaser wrote:
> I’ve just done so: both the “precomputed, up to 8192 bits” part
> (which already makes Qualys not cap the grade to B, but is not
> the proper fix, because, in the end, people will just pregenerate
> for the Debian-shipped group too) and the “load DH parameters from
> the first SSLCertificateFile” part.

There is every indication that precomputation for a 2048 bit DH group 
is still unfeasibly even for the NSA.

And custom DH groups are not that easy to handle in an automated way. 
For example on a cubietruck (Cortex A7), generation of a 2048 bit 
group takes about one hour.

> I’ve tested both parts with openssl(1) 1.0.2a (self-compiled from
> sources) and had a look at both the weakdh and the Qualys checker.
> 
> Please, feel free to make this into a proper wheezy-security upload
> until such time as more stuff from 2.2.30 is backported.
> 
> My backport is, basically, a reduced and edited SVN diff between
> upstream tags/2.2.29 and branches/2.2.x limited to the two parts
> I mentioned above (they come together in the same code, so…). I’ve
> only edited the documentation slightly (remove the reference to
> Apache 2.2.30 in two places) and resolved merge conflicts, but did
> not change anything besides.

Upstream jumped through quite a few hoops to make the patch work with 
openssl 0.9.8. We don't need that for wheezy (which has 1.0.1e), but 
it may come handy for squeeze when someone wants to do the backport.


Reply to: