Hardening TLS ciphers#492
Hardening TLS ciphers#492tomav merged 5 commits intodocker-mailserver:masterfrom tyranron:hardening-tls-ciphers
Conversation
|
Can't find normal and supported Yet another one to impl... |
|
Hi @tyranronn thanks for pointing this to us. |
|
@tomav yeap, that's the opposite side of such change. Better security -> less clients supported. As for me, better security is preferable by default. I think that the security level required by PCI compliance is more than enough for default settings and will help image users a lot if they require to meet PCI compliance standards. Only few old ciphers were removed, actually. Even more: those ciphers were not used by Postfix before change (Postfix from Also, this always may be tuned up in custom configuration, if someone needs to support less strong ciphers in his installation. I'm planing to cover this theme in wiki. |
|
It would be nice to choose how much security you want to enable. |
|
@tomav it's done now. Would you be so kind to review it? As I described above: there should be no impact for image users, as removed ciphers were not used by Postfix anyway. |
|
Hi @tyranron, LGTM but Travis is red. |
|
@tomav it's all about races =/ |
|
Great! |
* Hardening Dovecot TLS ciphers * Mitigate Logjam vulnerability on Dovecot * Mitigate Logjam vulnerability on Postfix * Add Nmap tests of PCI compliance for Postfix and Dovecot * Increase sleep duration on Makefile steps to avoid races
To follow the principle: Secure by default
Problem
Currently Dovecot does support TLS Medium Strength Cipher Suites.
Also both Postfix and Dovecot are vulnerable to Logjam attack.
Despite the fact of hard attack difficulty, the default setup is not PCI compliant:
Solution
Tune up default configuration to:
This is enough to have
least strength: Aand no warnings onnmaprun, which makes image PCI compliant.Notice
Dockerfile(notstart-mailserver.sh) because it's quite long operation and slows down container start.TODO
nmaptests