Unfortunately I was not able to pinpoint the configuration file for the turris administration web interface. So maybe one of you can point me out where it is. Iāll be happy to create a pull request for a hardened configuration.
Here follow the details for all the issues above.
SSL/TLS: Report Vulnerable Cipher Suites for HTTPS
āVulnerableā cipher suites accepted by this service (443/tcp)
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)
TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)
TLS_RSA_WITH_3DES_EDE_CBC_SHA (SWEET32)
Solution: The configuration of this services should be changed so that it does not accept the listed cipher suites anymore.
SSL/TLS: Report Weak Cipher Suites
āWeakā cipher suites accepted by this service (443/tcp)
TLS_ECDHE_RSA_WITH_RC4_128_SHA
TLS_RSA_WITH_RC4_128_MD5
TLS_RSA_WITH_RC4_128_SHA
TLS_RSA_WITH_SEED_CBC_SHA
Solution: The configuration of this services should be changed so that it does not accept the listed weak cipher suites anymore.
SSL/TLS: Diffie-Hellman Key Exchange Insufficient DH Group Strength Vulnerability
The SSL/TLS service uses Diffie-Hellman groups with insufficient strength (key size < 2048).
Solution: Deploy (Ephemeral) Elliptic-Curve Diffie-Hellman (ECDHE) or use a 2048-bit or stronger Diffie-Hellman group
System Information
Device: Turris Omnia
Turris OS version: 3.11.16
Kernel version: 4.4.187-a890a5a94ebb621f8f1720c24d12fef1-0
foris version: 100.3-3.6-1
You dont have to directly expose it to the internet. Still it is a best practice to disable RC4 and 3DES because it is unsafely. There are some techniques to target the router through browser scanning local network ranges even if remote access is disabled.
my router interface is not exposed to the internet. The scans were done internally.
Thank you. I managed to harden the configuration, so that the weak ciphers are not used any more. The following options have to be added to both IPv4 and IPv6 sockets in the /etc/lighttpd/conf.d/ssl-enable.conf:
SSLv2 and SSLv3 has already been disabled in my PR. I would let TLSv1.2 enabled, since that could potentially lock out a lot of devices and the gain in security is not as big as the probable loss in usability.
About disabling TLSv1.1 and TLSv1: Iām not sure if those should be disabled or not.
Thank you everyone again for your feedback. I added the changes to the pull request (TLSv1.2 only, ssl.openssl.ssl-conf-cmd).
Regarding the cipher suites: itās also subjected to review from cynerd on github. I will wait for the response there before updating the pull request.
Thank you @anon50890781 for the Mozilla config generator link. Thatās a really helpful tool I didnāt know.