Hi Lukas, On Sat, Apr 26, 2014 at 01:53:58PM +0200, Lukas Tribus wrote: > Also, one important thing to understand here is that this matters only with > *_DHE_* cihpers. Its not used with legacy non-PFS RSA cihpers or with ECDHE > ciphers. (...) > I would rather warn when the crt files doesn't contain dhparams and that > we are falling back to a possible suboptimal automation.
For the reason above, I'd rather not do this, because it means we'd emit warnings for all users even if they don't use DHE and are not impacted, thus forcing them to append useless data at the end of the certs. Not only that, but it also means people have to modify their currently valid cert files, which is rarely welcome in production. > Or, third possibility, remove all fallbacks, disabling _DHE_ but warn on > startup that we don't do _DHE_ ciphers since the crt file doesn't have > dhparams. It could be an option if we can easily detect and disable DHE in the ciphers list. Are there clients which risk not to be able to connect without it ? Willy
