Repository navigation
Update OpenBSD.org.xml - #2398
Conversation
|
Update/Alteration Announcement (HTTPS Everywhere Change Needed) for OpenBSD.org subdomains Hi, The TLS certificate for www.openbsd.org has been updated to include these new fields: My testing (with curl --tlsv1.2 $site, and https://$site in chrome 54.0.2840.59, and https://$site in firefox 49.0.1 ) has confirmed that HTTPS is working for: curl --tlsv1.2 $site works fine for the above domains and receives the 301 redirect over TLS on the aforementioned domains. Could the HTTPS Everywhere ruleset please be updated to reflect the New Domains enabled for TLS by the OpenBSD Project? For example, in the current ruleset at https://www.eff.org/https-everywhere/atlas/domains/openbsd.org.html it mentions: ftp.openbsd.org has been updated to support TLS. firmware and portroach are still problematic subdomains. Thank You for the Superb HTTPS Everywhere Project =) |
|
Thanks for the updates! |
|
Ruleset Update for OpenBSD.org subdomains New subdomains for *openbsd.org have been enabled for TLS. Testing was conducted on all the domains below using: All the subdomains below work fine via TLS: Note: ftp*.usa. show 403 at the / root of the webserver, which is irrelevant as everything is fine under the /pub/ subdirectory. I attached a pull request with the changes added to the OpenBSD.org.xml file, pull request = #9453 |
No description provided.