https://bz.apache.org/ooo/show_bug.cgi?id=127789
Dave Fisher <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #40 from Dave Fisher <[email protected]> --- Both the older pre 4.0 and >= 4.0 update services are hosted on the same apache.org web servers and they only support TLS 1.2 with just a few ciphers. The templates and extensions servers at SourceForge only support TLS 1.2 with many more ciphers. % nmap --script ssl-enum-ciphers -p 443 ooo-updates.apache.org Starting Nmap 7.80 ( https://nmap.org ) at 2020-08-19 12:55 PDT Nmap scan report for ooo-updates.apache.org (40.79.78.1) Host is up (0.073s latency). Other addresses for ooo-updates.apache.org (not scanned): 2a01:4f9:2a:185f::2 95.216.24.32 PORT STATE SERVICE 443/tcp open https | ssl-enum-ciphers: | TLSv1.2: | ciphers: | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp256r1) - A | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (secp256r1) - A | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (secp256r1) - A | compressors: | NULL | cipher preference: server |_ least strength: A Nmap done: 1 IP address (1 host up) scanned in 4.66 seconds Perhaps this issue is related to the newer updates being rewritten to a different domain name? -- You are receiving this mail because: You are the assignee for the issue.
