Comments (13)
I think the issue is caused by the fact that 10.5.0 is signed by Michaël Zasso, but import-release-team-keyring does not list his (current?) key. Manually adding it to gpg solved the issue for me (taken from nodejs release-team:
❯ gpg --keyserver pool.sks-keyservers.net --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
❯ asdf install nodejs 10.5.0
from asdf-nodejs.
Try to update asdf-nodejs plugin itself first and then update release keys:
asdf plugin-update nodejs
bash ~/.asdf/plugins/nodejs/bin/import-release-team-keyring
asdf install nodejs 10.5.0
from asdf-nodejs.
I submitted a PR that fixes the scripts. Just have to wait for approval.
from asdf-nodejs.
As a temp workaround, I set the env var NODEJS_CHECK_SIGNATURES=no
and it worked fine.
Obviously this negates the whole signing key security, but it at least allows you to install ;)
from asdf-nodejs.
I confirm ... Michaël Zasso's key (8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600) is missing from the import-release-team-keys script, while former release team member Italo A. Casas is still included (56730D5401028683275BD23C23EFEFE93C4CFFFE)
Fixing that script and running it did get the right keys into my system and then the install verify worked fine.
from asdf-nodejs.
The keys are hardcoded in this project: https://github.com/asdf-vm/asdf-nodejs/blob/master/bin/import-release-team-keyring#L6-L13
So, it is the responsibility of this plugin to maintain the current list. A couple options I see:
- Approach the nodejs team about providing this information in a basic web service format
- Build a webservice that crawls/or events on merges to the nodejs readme and updates the webservice accordingly.
- continue to update manually here.
from asdf-nodejs.
I have the same problem and tried getting the list of keys from nodejs repo instead: https://github.com/nodejs/node#release-team . The list is complete but I still couldn't install nodejs properly in my machine. This is the recent output in my console:
Wai-Yans-Macbook-Pro% asdf install nodejs v10.5.0
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6738 0 6738 0 0 5018 0 --:--:-- 0:00:01 --:--:-- 5020
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.
Authenticity of checksum file can not be assured! Please be sure to check the README of asdf-nodejs in case you did not yet bootstrap trust. If you already did that then that is the point to become SUSPICIOUS! There must be a reason why this is failing. If you are installing an older NodeJS version you might need to import OpenPGP keys of previous release managers. Exiting.
from asdf-nodejs.
I adjusted the import-release-team-keys
script and ran it and I get a gpg: keyserver receive failed: No data
for every key.
Probably another problem but maybe someone has an idea.
from asdf-nodejs.
Is there something in asdf-nodejs that needs to change to fix this issue? I'm not a regular Node.JS user myself so it's not obvious to me what is wrong here.
from asdf-nodejs.
If someone still have this issue, but with node 10.4.0 (asdf version 0.6.2),
I solved it with following:
gpg --keyserver ipv4.pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
It's a key form Myles Borins.
Actually, I had to manually install all keys form that PR - link, but I think, that helping one was only key mentioned above.
$ asdf install nodejs 10.4.0
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3856 0 3856 0 0 9427 0 --:--:-- --:--:-- --:--:-- 9404
gpg: Signature made Wed Jun 6 14:25:17 2018 UTC
gpg: using RSA key 0EFFE1BCEFD9C84E3D098152933B01F40B5CA946
gpg: Good signature from "Myles Borins <[email protected]>" [unknown]
gpg: aka "Myles Borins <[email protected]>" [unknown]
gpg: aka "Myles Borins <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: C4F0 DFFF 4E8C 1A82 3640 9D08 E73B C641 CC11 F4C8
Subkey fingerprint: 0EFF E1BC EFD9 C84E 3D09 8152 933B 01F4 0B5C A946
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 17.4M 100 17.4M 0 0 9601k 0 0:00:01 0:00:01 --:--:-- 9596k
node-v10.4.0-linux-x64.tar.gz: OK
from asdf-nodejs.
Same with node-js 11.10.1
from asdf-nodejs.
@lyo5ha if you've found another key that needs to be added feel free to create a PR to add it to the list in https://github.com/asdf-vm/asdf-nodejs/blob/master/bin/import-release-team-keyring
from asdf-nodejs.
I had to first brew install gpg
, then @shvetsovdm's answer worked like a charm for me.
from asdf-nodejs.
Related Issues (20)
- npm shim should work without $HOME HOT 5
- Unable to install 18.18.1 HOT 1
- import-release-team-keyring not found HOT 1
- NodeJS 18.18.2 is not in the list! HOT 2
- Can't install 21.0.0 HOT 4
- bug: asdf cannot resolve config paths with whitespace in them HOT 2
- Last version is 20.5.1 but Node is already at 21.0.2 HOT 1
- asdf cant find definition for v18.19.0 HOT 2
- Dependency on nvm HOT 1
- How to install Nodejs latest LTS version? HOT 1
- default-npm-packages support registry
- asdf: Warn: You have configured asdf to preserve downloaded files (with always_keep_download=yes or --keep-download). But asdf: Warn: the current plugin (nodejs) does not support that. Downloaded files will not be preserved. HOT 2
- not using project .tool-versions to set node version in tmux
- Is it possible to show the LTS version in the list of versions right after installing the plugin?
- Cannot install node 21.7.x HOT 2
- Cannot install latest lts [email protected] HOT 2
- feat: Node.js nightly (v22) install
- WARNING: node-v21.7.2-darwin-arm64 is in LTS Maintenance mode and nearing its end of life. It only receives *critical* security updates, *critical* bug fixes and documentation updates. HOT 3
- Failed to find Node 20.13.0 (LTS) HOT 3
- asdf suggests nodejs version is not installed when actually yarn isn't
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from asdf-nodejs.