Opened 9 years ago

Closed 10 months ago

#1537 closed enhancement (fixed)

Configure ssl for FOSS4G 2016

Reported by: neteler Owned by: robe
Priority: normal Milestone: Sysadmin Contract 2024-I
Component: SysAdmin Keywords: ssl
Cc:

Description

As per subject line - it is a DigiCert SSL certificate, probably it needs to be replaced with the OSGeo wildcard certificate?

Change History (14)

comment:1 by EliL, 9 years ago

Summary: 2014.foss4g.org SSL certificate expiredConfigure ssl for FOSS4G archives
Type: defectenhancement

Now that DNS has been updated (#1525), this is a different problem. Now it is that it is for the incorrect domain:

2014.foss4g.org uses an invalid security certificate. The certificate is only valid for the following names: *.osgeo.org, osgeo.org

which is also the same for other years.

I've changed this to an enhancement to "Configure ssl for FOSS4G archives". Closing this would be fine too.

comment:2 by wildintellect, 7 years ago

We should configure Let's encrypt for this. I believe the archives are hosted on WebExtra.

comment:3 by neteler, 11 months ago

The conference copy https://2016.foss4g.org/

uses a broken SSL certificate (only issued for files.fossgis.de).

in reply to:  3 comment:4 by robe, 11 months ago

Replying to neteler:

The conference copy https://2016.foss4g.org/

uses a broken SSL certificate (only issued for files.fossgis.de).

Looks like that is an A record to 49.12.96.25

We don't have control over that server. Ideally I guess it would be best to create an archive of it on osgeo infra, since it's a past conference and then we can add an ssl to it and keep it forever.

I haven't looked to see how crawlable it is or if there is a git of it somewhere we can clone. You know who manages that?

The short-fix I guess is we could just proxy it thru our own nginx, but still have it go to 49.12.96.25, but that seems a bit roundabout.

comment:5 by robe, 11 months ago

Owner: changed from sac@… to robe

comment:6 by robe, 11 months ago

Milestone: Sysadmin Contract 2024-I

comment:7 by neteler, 11 months ago

I have ping'ed the sysadmin of FOSSGIS e.V. who will provide the static copy. From that we can deploy it locally and conserve it "forever".

comment:8 by nilsnolde, 11 months ago

Hi, you can find the copy here: https://next.gis-ops.com/s/BM6GWDb6d42T8K6. Let me know once it's downloaded and I'll remove it again.

comment:9 by nilsnolde, 10 months ago

Any updates here?

comment:10 by robe, 10 months ago

@nilsnolde,

I'll get to it this week. Sorry for the delay.

in reply to:  8 ; comment:11 by robe, 10 months ago

Replying to nilsnolde:

Hi, you can find the copy here: https://next.gis-ops.com/s/BM6GWDb6d42T8K6. Let me know once it's downloaded and I'll remove it again.

You can remove now though, I've already downloaded.

comment:12 by robe, 10 months ago

Okay I have it hosted now on osgeo9 in wordpress container. Will probably take a bit for it to propagate, but at a glance looks to be okay.

in reply to:  11 comment:13 by nilsnolde, 10 months ago

Replying to robe:

You can remove now though, I've already downloaded.

Perfect, thanks for the heads-up!

comment:14 by robe, 10 months ago

Resolution: fixed
Status: newclosed
Summary: Configure ssl for FOSS4G archivesConfigure ssl for FOSS4G 2016

I'm going to close this one out since 2016.foss4g.org is now hosted on osgeo infra, and changed the subject to make it clear it's just for foss4g2016. We'd need to handle any others that don't have ssl on a case by case basis, so separate tickets will need to be put in for each of those.

Note: See TracTickets for help on using tickets.