Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Update OpenBSD.org.xml - #2398

Merged
jsha merged 1 commit into
EFForg:masterfrom
J0WI:patch-38
Aug 12, 2015
Merged

jsha merged 1 commit into
EFForg:masterfrom
J0WI:patch-38

Conversation

@J0WI

@J0WI J0WI commented Aug 3, 2015

Copy link
Copy Markdown
Contributor

No description provided.

jsha added a commit that referenced this pull request Aug 12, 2015
@jsha
jsha merged commit 7b9765a into EFForg:master Aug 12, 2015
@J0WI
J0WI deleted the patch-38 branch August 12, 2015 22:57
@massoc

massoc commented Oct 19, 2016

Copy link
Copy Markdown
Contributor

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:
"Subject Alternative Name=
DNS Name=ftp.openbsd.org
DNS Name=libressl.org
DNS Name=openbsd.org
DNS Name=openssh.com
DNS Name=www.libressl.org
DNS Name=www.openbsd.org
DNS Name=www.openssh.com
"

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:
https://openbsd.org (301 moved permanently to www.openbsd.org)
https://ftp.openbsd.org/
https://libressl.org/ (301 moved permanently to www.libressl.org)
https://openssh.com (301 moved permanently to www.openssh.com)
https://www.libressl.org
https://www.openbsd.org/
https://www.openssh.com/

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:
"Nonfunctional hosts in *openbsd.org
ftp, ftp.eu, ftp2.eu, &c, man"

ftp.openbsd.org has been updated to support TLS.
ftp.eu, ftp2.eu, man, cvsweb, are still not responding via TLS.

firmware and portroach are still problematic subdomains.

Thank You for the Superb HTTPS Everywhere Project =)

@mnordhoff

Copy link
Copy Markdown
Contributor

#7377 #7378 #7379

@J0WI

J0WI commented Oct 20, 2016

Copy link
Copy Markdown
Contributor Author

Thanks for the updates!

@massoc

massoc commented Apr 6, 2017

Copy link
Copy Markdown
Contributor

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:
curl --tlsv1.2 $site
https://$site in firefox 52.0.2
https://$site in chrome 57.0.2987.133

All the subdomains below work fine via TLS:
https://ftp.OpenBSD.org
https://ftp.fr.openbsd.org
https://ftp.eu.openbsd.org
https://ftp3.usa.openbsd.org/pub/
https://ftp4.usa.openbsd.org/pub/
https://ftp5.usa.openbsd.org/pub/
https://cvsweb.openbsd.org
https://ftp.usa.openbsd.org/pub/
https://portroach.openbsd.org/

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants