-
Notifications
You must be signed in to change notification settings - Fork 142
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
Missing RSA key ID 821C587A from the release team, keyserver changed #65
Comments
I have got the same issue. |
The fix is to update nodejs plugin, or all plugins: asdf update-plugin --all and then re-import the pgp keys: |
The workaround works fine. Only a little clarification. |
Why does this say: "WARNING: This key is not certified with a trusted signature!"
|
The workaround above does not work for me.
I've tried clearing all keys (deleting each one manually with
Guess I should also include this output:
|
@drusepth - any resolution? |
@drusepth I got the same issue... can't find a solution yet... please let me know if anyone has found a fix. Thanks |
No fix has been found. I switched to using n to manage my nodejs versions. |
I have no real idea why, but this fixed it for me: rm -rf ~/.asdf/keyrings/nodejs
~/.asdf/plugins/nodejs/bin/import-release-team-keyring |
Can you all try the latest version? I think this has been fixed. |
@Stratus3D Just tried 8.11.3 & 10.7.0 and they both work flawlessly. Thanks! |
Seems to now be working for me as well. 👍 |
We may eventually need to add a |
I added a comment to Issue #40 about the missing key with id 821C587A.
The cause is that there is a new Node release team member with that key.
Furthermore they changed keyserver from
ipv4.pool.sks-keyservers.net
topool.sks-keyservers.net
.A quick fix is to download the missing key with
but
~/.asdf/plugins/nodejs/bin/import-release-team-keyring
should be updated with the commands at https://github.com/nodejs/node#release-teamThe text was updated successfully, but these errors were encountered: