Page MenuHomeSoftware Heritage

Fix invalid status.s.o certificate
Closed, MigratedEdits Locked

Description

I don't know if it's redundant or not with the parent task (which references that domain twice, 1 for gandi, 1 for status.io).
So i'm opening it either way, we can always fix that later.

irc discussion:

15:25 <+ardumont> fyi, added deposit.s.o in status.io page: https://status.softwareheritage.org/
15:28 <+zack> ardumont: while you're it, it looks like the status.s.o SSL certificate is invalid, filing a task (or fixing it right away, if possible :-)) about that would be nice
15:29 <+zack> i daresay it's a requirement to make that page usable/trustable for visitors
15:29 <+ardumont> that's already referenced in the task opened i think (checking the number)
15:29 <+zack> oh, ok, cool
15:29 <+ardumont> T979
15:29 -- Notice(swhbot): T979 (submitter: olasd, owner: olasd, priority Wishlist, status: Work in Progress): Migrate TLS certificates away from the *.softwareheritage.org wildcards <https://forge.softwareheritage.org/T979>
15:29 <+zack> mmmmh, i don't think it's the same issue
15:29 <+zack> status.s.o has a currently *invalid* certificate
15:29 <+zack> not a wildcard (but valid) one

Event Timeline

ardumont triaged this task as Wishlist priority.Jul 15 2019, 3:55 PM
ardumont created this task.
olasd claimed this task.

At the point of this report, status.softwareheritage.org was /not/ supposed to be accessible via https.

In the meantime, status.io has now been setup to allow the automatic generation of certificates (via cloudfront's offer; that meant adding a TXT record to the softwareheritage.org DNS zone) for that domain, and https://status.softwareheritage.org/ now works.