Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The certificate of archive.raspberrypi.org has expired #175

Closed
PeterLacknase opened this issue May 30, 2020 · 7 comments
Closed

The certificate of archive.raspberrypi.org has expired #175

PeterLacknase opened this issue May 30, 2020 · 7 comments

Comments

@PeterLacknase
Copy link

PeterLacknase commented May 30, 2020

sudo apt update

woes

"https://archive.raspberrypi.org/debian buster Release Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification."

Seems like the *.raspberrypi.org wildcard certificate is still valid but it needs to use a different certification path:

"Certificate:
Data: Version: 3 (0x2)
Serial Number: 13:ea:28:70:5b:f4:ec:ed:0c:36:63:09:80:61:43:36
Signature Algorithm: sha384WithRSAEncryption
Issuer: C = SE, O = AddTrust AB, OU = AddTrust External TTP Network, CN = AddTrust External CA Root
Validity:
Not Before: May 30 10:48:38 2000 GMT
Not After : May 30 10:48:38 2020 GMT
Subject: C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority"

@XECDesign
Copy link
Member

Thanks for opening the issue.

For reference: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=275648

@XECDesign
Copy link
Member

Should be sorted.

@PeterLacknase
Copy link
Author

It is. Thanks a lot.

@XECDesign
Copy link
Member

Thanks

@edreinoso
Copy link

Sorry, but I'm persisting with this problem, since it is driving me a bit crazy

I also get a similar message when I'm trying to do a simple: sudo apt upgrade

Certificate verification failed: The certificate is NOT trusted

The difference for me is that my certicate expires in 2028, so there should not be any issues as of why this problem should be arising in the first place.

Certificate:
Data:
Version: 3 (0x2)
Serial Number:
Signature Algorithm: sha384WithRSAEncryption
Issuer: C = GB, ST = Greater Manchester, L = Salford, O = Comodo CA Limited, CN = AAA Certificate Services
Validity
Not Before: Mar 12 00:00:00 2019 GMT
Not After : Dec 31 23:59:59 2028 GMT
Subject: C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority

@XECDesign
Copy link
Member

Has your system time been updated? You can check with the output of date. It takes a while after booting for systemd-timesyncd to do its thing.

@edreinoso
Copy link

edreinoso commented Jun 13, 2023

Thank you for your reply.

The system time has been updated. You can see the output below:

pi@raspberrypi:~ $ date
Tue 13 Jun 2023 01:53:57 PM CEST

pi@raspberrypi:~ $ timedatectl
Local time: Tue 2023-06-13 13:55:40 CEST
Universal time: Tue 2023-06-13 11:55:40 UTC
RTC time: n/a
Time zone: Europe/Amsterdam (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

I have this thread on Raspberry Pi community support for better reference.

https://forums.raspberrypi.com/viewtopic.php?p=2113419#p2113419

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants