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.

Sign up for GitHub

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

Jump to bottom

key expired #31

Open
dmdnipro-node opened this issue Sep 12, 2024 · 2 comments
Open

key expired #31

dmdnipro-node opened this issue Sep 12, 2024 · 2 comments

Comments

@dmdnipro-node
Copy link

890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4

gpg --list-keys --fingerprint

pub rsa3072 2022-05-17 [SC] [expired: 2024-05-16]
890C 08DB 8579 162F EE0D F9DB 8BEA B4DF CF55 5EF4
uid [ expired] RafaelGSS rafael.nunu@hotmail.com
@RafaelGSS
Copy link
Member

This has been solved in #29 (comment).

Fetch the keys again.

@KangyaoMa
Copy link 

[2025-01-13T08:28:01.785Z] + gpg --verify SHASUMS256.txt.sig SHASUMS256.txt

[2025-01-13T08:28:01.785Z] gpg: directory '/home/jenkins/.gnupg' created

[2025-01-13T08:28:01.785Z] gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created

[2025-01-13T08:28:01.785Z] gpg: Signature made Wed Apr 24 18:22:21 2024 UTC

[2025-01-13T08:28:01.785Z] gpg:                using RSA key 890C08DB8579162FEE0DF9DB8BEAB4DFCF555EF4

[2025-01-13T08:28:01.785Z] gpg: Can't check signature: No public key

script returned exit code 2

Same issue found for node v22.0.0

@UlisesGascon UlisesGascon mentioned this issue Jan 13, 2025
Closed
@aduh95 aduh95 marked this as a duplicate of #33 Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@RafaelGSS @KangyaoMa @dmdnipro-node