deb/rpm repo blocked again

[liar666]

I'm trying to install vscodium on debian.

Following instructions here : https://vscodium.com/#install-on-debian-ubuntu-deb-package

I'm getting error

W: GPG error: https://download.vscodium.com/debs vscodium InRelease: Unknown error executing apt-key
E: The repository 'https://download.vscodium.com/debs vscodium InRelease' is not signed.

I found a lot of previous issues about that problem but they are all closed while problem persists.

The instructions use URL: https://download.vscodium.com/debs
But this redirects to: https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/
Which is a HTTP 404...

[daiyam]

You have to install the GPG key as describe in the doc.
All the errors indicate it: GPG error, is not signed.

The repository is fine.

The 404 error is a soft error/false positive.

[aog2000a]

@daiyam Today, using the Debian repo, i am getting

Certificate verification failed: The certificate is NOT trusted. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 143.244.56.52 443]

Also connecting to https://download.vscodium.com/
via browser i get a security warning since the server certificate (which is valid for *.b-cdn.net) does NOT match the hostname.

This issue has nothing to do with GPG signature of the package files... By the way, i checked i still have the latest trusted signing key
https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/raw/master/pub.gpg
in my APT configuration.

@liar666 FYI

[UniDyne]

In addition to the CDN's SSL certificate being exposed rather than the vscodium domain, bunny.net seems to be yielding an account suspended page, which will cause apt to report the scary "Clearsigned file isn't valid...".

The README points us to @paulcarroty's repo, which hosts the apt repo over here: https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs

Should the website be updated to point to the maintainer's GitLab address rather than the CDN?

Also #2178, #2177.

[daiyam]

Should the website be updated to point to the maintainer's GitLab address rather than the CDN?

No because GitLab has a bandwidth limit which can be easily reached.

But the CDN issue isn't this issue related. For CDN issue, please go to #2178