Project

General

Profile

Feature #6593

squid: allow user to configure DH key size, SINGLE_DH_USE, NO-SSLv3, Cipher-Suites - performance improvement hint

Added by Alexander Wilke 8 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Category:
-
Target version:
Start date:
07/09/2016
Due date:
% Done:

100%


Description

Squid has some additional options set like:

options=NO_SSLv2,NO_SSLv3,SINGLE_DH_USE (and should have "SINGLE_ECDH_USE")

First:
For the user it would be good to have the possibility to modify "NO_SSLv3" using the WebUI to make sure that squid is compatible even with old and insecure protocols. In general noone should use old protocols but it is the same with "untrusted" certificates. There is an option in the WebUI, too, to allow this - even this shouldn't be in a secure environment.

Second:
I understabnd SINGLE_DH_USE this way, that in egnerates a new key for every new connection. So in egneral a DH key only is valdi as long as the connection is. This shouldn't be longer than several hours or so.
From a security point of view DH key size with less than 2048bit is insecure. But this is only valid for DH keys which do not change. For DH keys which change for example with every connection (SINGLE_DH_USE) this should not be a security problem. But increasing the DH key from 1024 up to 2048 bit increases the performance impact by 5x-6x.

So there should be a valid discussion if there should be an option in the WebUI to configure 1024bit DH key and use SINGLE_DH_USE - which will be probably as sescure as or more secure than a static 2048bit DH key.

Third:
Allow the administrator to configure the allowed cipher-suites. Possibility could be tha there is a "recommended" profile which configures the cipher-suites like you did at the moment by default.
Then there could be a custom field where the user can enter the allowed ciphers like "!3DES:HIGH:!RC4" like he wants.

History

#1 Updated by Kill Bill 8 months ago

Alexander Wilke wrote:

For the user it would be good to have the possibility to modify "NO_SSLv3" using the WebUI to make sure that squid is compatible even with old and insecure protocols.

Sigh. Feel free to use System Patches to make such absolutely horrible modifications. Introducing changes into the package that go absolutely the opposite way than everyone else goes (including things like openssl and the browsers) is simply insane.

#2 Updated by Kill Bill about 2 months ago

https://github.com/pfsense/FreeBSD-ports/pull/241

Added options matching the reverse proxy options (modern/intermediate cipher suites, DH key size options). Making things any more complicated just confuses users and serves no generally useful purpose really, IMNSHO.

If you need SSLv3, feel free to patch yourself (plus, that won't be even a viable option with later OpenSSL versions.)

#3 Updated by Renato Botelho about 2 months ago

  • Status changed from New to Feedback
  • Assignee set to Renato Botelho
  • Target version set to 2.4.0
  • % Done changed from 0 to 100

PR has been merged, thanks!

#4 Updated by Jim Pingle about 1 month ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF