Page 1 of 1

Archive throwing an invalid SSL cert error

Posted: 2021-05-14, 17:53
by iborg
Hi
When I click the link to the PaleMoon archive (http://archive.palemoon.org/palemoon/), a Cloudfare 526 error page (invalid SSL certificate) comes up instead of the archive. Is this something that will be fixed or do I have to just go in there and take the risk?

I'm on OpenSUSE Leap 42.3, Palemoon version 29.1.1. Details from the error page:
(BTW I did try again in a few minutes)
What happened?

The origin web server does not have a valid SSL certificate.
What can I do?
If you're a visitor of this website:

Please try again in a few minutes.
If you're the owner of this website:

The SSL certificate presented by the server did not pass validation. This could indicate an expired SSL certificate or a certificate that does not include the requested domain name. Please contact your hosting provider to ensure that an up-to-date and valid SSL certificate issued by a Certificate Authority is configured for this domain name on the origin server. Additional troubleshooting information here.

Re: Archive throwing an invalid SSL cert error

Posted: 2021-05-14, 18:18
by Moonchild
http URL
means no SSL
Are you sure you're trying to go to the non-SSL address?

Re: Archive throwing an invalid SSL cert error

Posted: 2021-05-15, 05:50
by jobbautista9
Maybe they're using an "HTTPS Everywhere" type of extension.

Why would you need TLS for downloads anyway? Just learn to GPG if you're worried about security.

Re: Archive throwing an invalid SSL cert error

Posted: 2021-05-15, 10:16
by Night Wing
@ iborg

FWIW, I also use a linux distribution.

After clicking on the link which you provided, no problems were encountered reaching the page.

At this time, I am using 64 bit linux Pale Moon 29.2.0 running in 64 bit linux Mint 20.1 (Ulyssa) Xfce. I'm using Pale Moon's default settings.

Re: Archive throwing an invalid SSL cert error

Posted: 2021-05-15, 10:19
by Moonchild
jobbautista9 wrote:
2021-05-15, 05:50
Maybe they're using an "HTTPS Everywhere" type of extension.
There is no reason whatsoever in 2021 to still be using this.
If a website is using http, it will be doing so on purpose. If they support/prefer https, you will be forwarded. Let the server operator decide what to serve you.
jobbautista9 wrote:
2021-05-15, 05:50
Why would you need TLS for downloads anyway?
People are still afraid of the in-transit-replacement potential of http. You can use checksums, PGP and the code-signing (if on Windows) check to see if the download is correct.