update SSL configuration directives
Metacat ships with the metacat-site-ssl file showing how to configure Metacat for SSL support, and references this document in the Admin guide. Certain versions of SSL are now vulnerable, and so we need to ensure that our example configurations and documentation show how to exclude these vulnerabilities. See details below from the security advisory.
SSL Version 2 and 3 Protocol Detection (20007) Synopsis: The remote service encrypts traffic using a protocol with known weaknesses. Description: The remote service accepts connections encrypted using SSL 2.0 and/or SSL 3.0. These versions of SSL reportedly suffer from several cryptographic flaws. An attacker may be able to exploit these flaws to conduct man-in-the-middle attacks or to decrypt communications between the affected service and clients. NIST has determined that SSL 3.0 is no longer acceptable for secure communications. As of the date of enforcement found in PCI DSS v3.1, any version of SSL will not meet the PCI SSC'S definition of 'strong cryptography'. See Also: http://www.schneier.com/paper-ssl.pdf http://support.microsoft.com/kb/187498 http://www.nessus.org/u?247c4540 https://www.openssl.org/~bodo/ssl-poodle.pdf http://www.nessus.org/u?5d15ba70 Solution: Consult the application's documentation to disable SSL 2.0 and 3.0. Use TLS 1.0 or higher instead.
#1 Updated by Nick Brand over 5 years ago
Probably useful: https://mozilla.github.io/server-side-tls/ssl-config-generator/
Apache, Intermediate, HSTS unchecked.