Your message dated Sat, 7 Aug 2021 12:50:52 +0200 (CEST)
with message-id <2cf6d0ac-a12a-c176-a549-e19e1219e...@sourcepole.ch>
and subject line can't reproduce
has caused the Debian Bug report #991972,
regarding backports.org invalid certificate
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
991972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: www.debian.org
Some muscle memory from a long time ago kicked in, and I browsed to
backports.org instead of to backports.debian.org.
backports.org now seems to serve the Debian homepage, and in the process
triggers the browser's invalid certificate error, because the
certificate is for www.debian.org.
It seems to me that backports.org should redirect to
backports.debian.org. I'm not sure why the Debian homepage would greet
somebody visiting backports.org, but if that's desired, it should
redirect to www.debian.org rather than simply serve its content. In
either case backports.org should have its own proper certificate.
Or backports.org could go away.
--- End Message ---
--- Begin Message ---
Hi Xan,
you wrote:
backports.org now seems to serve the Debian homepage, and in the process
triggers the browser's invalid certificate error, because the
certificate is for www.debian.org.
It seems to me that backports.org should redirect to
backports.debian.org
I can not reproduce this. If I point my Debian bullseye Firefox to
http://backports.org then the browser gets redirected and ends up on the
URL https://backports.debian.org/. No problems with certificates occur.
https://backports.org (note the 's' in https) is not served by the
backports.org server at all, which seems to be a perfectly fine behavior
to me.
Thus I am unable to find out how something is broken at backports.org.
Further on `whois` tells me that backports.org is - as far as I can see -
not managed by Debian:
$ whois backports.org
Domain Name: BACKPORTS.ORG
Registry Domain ID: D98201512-LROR
Registrar WHOIS Server: whois.antagus.de
Registrar URL: http://www.vautron.de
Updated Date: 2021-05-28T01:25:42Z
Creation Date: 2003-05-27T12:55:02Z
Registry Expiry Date: 2022-05-27T12:55:02Z
Registrar Registration Expiration Date:
Registrar: Vautron Rechenzentrum AG
... so if you want to get anything fixed then you should talk to those
people?
I'm closing this ticket due to the reasons stated above. Please, if you
want to provide further info, that helps to clarify how to reproduce the
problems that you are seeing, then please do send an email to
991972 @bugs.debian.org and reopen this ticket.
Thank you!
*t
--- End Message ---
