Created attachment 699606 [details] exim-dhparam-regen Description of problem: Adding tls_privatekey allows the use of more ciphers. The manual (section 39.6) says: ''' If tls_dhparam = /some/file/name is set, the SSL library is initialized for the use of Diffie-Hellman ciphers with the parameters contained in the file. This increases the set of cipher suites that the server supports. See the command openssl dhparam ''' The following should be added after the existing config line: tls_privatekey = /etc/pki/tls/private/exim.pem # This (RedHat) build of exim is built with OpenSSL so this is useful as it # increases the number of cipher suites supported. This file will be regenerated # daily by /etc/cron.daily/exim-dhparam-regen tls_dhparam = /etc/pki/tls/certs/exim-dh2048.pem The script exim-dhparam-regen is attached. In the startup script /etc/init.d/exim in function gen_cert add: /etc/cron.daily/exim-dhparam-regen LEAVE_EXISTING The above is not urgent, but would be nice.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.