This is something that I hope people updating their Debian machines over tor (which is a must if you care for your privacy and security) could find courious and useful.
But only if also they need Node.js for some reason. There should be, once I expand the matters, some deeper insight/investigation into a repository key issue.
For doing all the installing and updating over tor, readers who are yet to learn of this goodness, pls read:
https://blog.torproject.org/debian-and- ... -services/
And about Node.js, it's at https://nodejs.org/. I happen to need this program now.
Recently Node.js have done this:
It should go smoothly as per:
https://github.com/nodesource/distributions
However there are issues:
https://github.com/nodesource/distributions/issues/1723
(the issue is entitled "[ERROR] User-Agent Discrimination on Repository Web Server results in "HTTP Error 403: Forbidden" #1723")
I've stumbled upon something that looks very similar to what is pointed to there, and it appears to me it's not just Ansible nor my Debian that get issues with the installing as per the distribution page linked above.
While it probably would work to just download the right tar.gz from https://nodejs.org/en/download/ I prefer installing things in Debian using the repository that they have set up.
I first thought about following the tip at Installation instructions:
Node.js LTS (v20.x):
I'll be substituting curl with t_curl in lines below that I will paste.
but then I saw there is also the:
Repository-Manual-Installation.
Just as it reads there:
Configuration Steps for Debian systems, Initialize the New Repository
where it reads:
and the post would get unreadable if I posted here what nodesource-repo.gpg.key looks like. They look like doing some Javascript magic with gpg, along with CloudFlare rays and I can't figure out how that can work. I need another post now.
But only if also they need Node.js for some reason. There should be, once I expand the matters, some deeper insight/investigation into a repository key issue.
For doing all the installing and updating over tor, readers who are yet to learn of this goodness, pls read:
https://blog.torproject.org/debian-and- ... -services/
And about Node.js, it's at https://nodejs.org/. I happen to need this program now.
Recently Node.js have done this:
which read in: https://github.com/nodesource/distribut ... ns/#123456Revamping our repo: Closing over 75% of our issues with these changes
It should go smoothly as per:
https://github.com/nodesource/distributions
However there are issues:
https://github.com/nodesource/distributions/issues/1723
(the issue is entitled "[ERROR] User-Agent Discrimination on Repository Web Server results in "HTTP Error 403: Forbidden" #1723")
I've stumbled upon something that looks very similar to what is pointed to there, and it appears to me it's not just Ansible nor my Debian that get issues with the installing as per the distribution page linked above.
While it probably would work to just download the right tar.gz from https://nodejs.org/en/download/ I prefer installing things in Debian using the repository that they have set up.
I first thought about following the tip at Installation instructions:
Node.js LTS (v20.x):
Using Debian, as rootcurl -fsSL https://deb.nodesource.com/setup_lts.x | bash - &&\apt-get install -y nodejsNote: I don't install things over clearnet. I woudn't run that line without modification. I have
/usr/local/bin/t_curl#!/bin/shtorsocks /usr/bin/curl $@So the line would be: t_curl -fsSL ...
I'll be substituting curl with t_curl in lines below that I will paste.
but then I saw there is also the:
Repository-Manual-Installation.
Just as it reads there:
And, in essence, this is the issue that I can't solve. Their repo key.if you prefer a manual approach or wish to understand the process in detail, the following guide is available
Configuration Steps for Debian systems, Initialize the New Repository
where it reads:
# Download the new repository's GPG key and save it in the keyring directoryt_curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpgwhich I get only:
curl: (22) The requested URL returned error: 403 gpg: no valid OpenPGP data found.So I try simply:
t_curl -L https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key -o nodesource-repo.gpg.keyas the -fsS is just cosmetic:
and the post would get unreadable if I posted here what nodesource-repo.gpg.key looks like. They look like doing some Javascript magic with gpg, along with CloudFlare rays and I can't figure out how that can work. I need another post now.
Statistics: Posted by elimork — 2024-01-20 23:07 — Replies 0 — Views 68