desktop: invalid SSL cert for `*.packages.shiftkey.dev`
Hey @shiftkey,
it seems that your ssl cert for https://apt.packages.shiftkey.dev/ is the default azure one and causes an error for apt
Error: https://apt.packages.shiftkey.dev/ubuntu any InRelease 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: 13.107.246.44 443]
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 9
- Comments: 40 (2 by maintainers)
Commits related to this issue
- fix: use shiftkey mirror to get kpgkey see https://github.com/shiftkey/desktop/issues/1062 — committed to stefan-karlsson/dotfiles by stefan-karlsson 2 years ago
đ Apologies for the delay - Iâve been on holidays the past couple of weeks so this had to sit broken.
This has now been restored and Iâll do a bit of a write-up on the next steps when I have bandwidth to document this further.
Please donât post me too commentsâŠ
There is nothing to be done on the client side. We have to wait for @shiftkey to fix thie
Just thought I would add that âinvalidâ in this case does not mean âexpired,â as tends to be the case when TLS goes awry and is what I expected to find when I myself encountered this issue just now. Rather, the Subject (Common Name) of the certificate no longer matches the domain name, instead being issued for
azureedge.netrather than*.packages.shiftkey.dev. As the domain is also enrolled in HTST (good choice, BTW), the subject mismatch has completely disabled access to the domain. Hopefully this helps you to dig right into the meat of the problem when you have the time to troubleshoot it.Thanks for maintaining such a useful resource for us Linux diehards out there. đđ»
Can we please lock this issue to reduce the spam?
To people reading this comment, the reason the repo isnât working is because the Azure instance runs out of bandwidth, and because of that the HTTPs certificate is changed to the default Azure one and not the one for shiftkey.
Use the MWT mirror as described in the README.
TL;DR this is a known issue and posting here wonât help.
February 11
Have the same issue in the Debian repository.
Yep, the same issue has been revived.
I havenât done this write-up yet so Iâm gonna reopen this for now to remind myself to not forget this issueâŠ
its joever đ
Same issue in RPM repo
Similar issue on Fedora Linux 40:
upon (temporarily) disabling HSTS in my browser i got this:
@tylerebowers @Margaret6556 It ran out of bandwidth. You can use the mwt repo in the readme.
I only use shiftkey for github-desktop. I wonât get updates while it is disabled. The pros are I can update my system now.
SSL issue certifcate NOT matching from Fedora41
Server certificate subject=C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=*.azureedge.net issuer=C=US, O=Microsoft Corporation, CN=Microsoft Azure RSA TLS Issuing CA 07
I tried to debug 2x, no success. Pls advise and fix. Thanks
December 13th here. Looks like an another certificate problem:
W: Failed to fetch https://apt.packages.shiftkey.dev/ubuntu/dists/any/InRelease 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: 13.107.246.71 443]Feel free to steer more traffic to my mirror to reduce bandwidth usage.
The most extreme would be to remove the source repo from the readme and only list it as the source for gpg keys.
(For security context, I donât have shiftkeyâs private key. I just download and serve up the files that he has signed.)
Certificate is failing again in the RPM repo
Thank you @shiftkey! RPM repo is working again (at least for Fedora 40)