[MDEV-30427] Infrastructure: ssl certificate error Created: 2023-01-18  Updated: 2023-08-07  Resolved: 2023-08-07

Status: Closed
Project: MariaDB Server
Component/s: N/A
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Marc Assignee: Faustin Lammler
Resolution: Fixed Votes: 0
Labels: None


 Description   

the website https://bugs.mariadb.org/ is an alias of https://jira.mariadb.org/

but the ssl certificate is invalid. Search via e.g. ecosia finds bugs rather than the jira website. And the browser shows warnings about the invalid certificate

I suggest adding another certificate for this alias site or add an wildcard certificate



 Comments   
Comment by Daniel Black [ 2023-01-18 ]

I didn't think we'd used bugs.mariadb.org in quite a while. Is there a popular link out there somewhere?

Comment by Marc [ 2023-01-19 ]

first hit in e.g. ecosia:
ecosia search

you should add an redirect. Users usally search for "bugs" and "mariadb"

Comment by Kirk Brown [ 2023-08-05 ]

faust this was assigned to me, but is referring to a foundation domain - if you're going to redirect bugs.mariadb.org to jira.mariadb.org, you might want to set that up using Cloudflare rules - that will work without us having to do anything on the server side. You might also consider letting this URL just shut down if it's no longer necessary. Let me know if you need anything from us here!

Comment by Faustin Lammler [ 2023-08-05 ]

kbrown sure, at the moment it's a CNAME pointing to jira.mariadb.org, so nothing needs to be done WRT the migration but we need to fix the TLS problem.

danblack, TheLinuxJedi, cvicentiu, greenman, please let me know if I can remove that domain name.

Comment by Ian Gilfillan [ 2023-08-05 ]

I'm not aware that we've ever used it, but obviously it was added as an alias at some point. Lots of JIRA issues are indexed under that domain (on DDG too, not just Ecosia), but the only external mention I can find besides search engine results is at https://atlas.eff.org//domains/mariadb.org.html

Comment by Faustin Lammler [ 2023-08-07 ]

Let's remove it then...

Generated at Thu Feb 08 10:16:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.