node-ipc
gitian-builder
node-ipc | gitian-builder | |
---|---|---|
76 | 7 | |
42 | 398 | |
- | - | |
2.3 | 2.5 | |
8 months ago | about 2 months ago | |
JavaScript | Python | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
node-ipc
-
gotta admit, gadgetbridge is awesome!
It should be noted that when developers have the ability to upload packages themselves, there is no guarantee that what the user gets corresponds to the source code that is available. The malware in node-ipc is suspiciously absent from the published source repository which has the latest release in 2021. If you were pulling directly from the source code you would not have seen this. This is an issue with npm, not libre software or "open source."
- How far it's fallen. Bring back my dog.
- Any updates on Rust, and node ipc?
- Anonymous Takes Anti-Putin Battle to Russian People with Printer Attack to Disrupt Kremlin's Propaganda
- Embedded Malicious Code in node-ipc
- Commentary on the Node-IPC incident and open source supply chains
-
The authors of node-ipc have pushed malware in an update, which wipes your disk if you happen to have Russian or Belorussian IP address. This affects some large projects like Vue CLI where it is a dependency.
Direct link to the github discussion: https://github.com/RIAEvangelist/node-ipc/issues/233 (many comments have been removed)
-
Sabotage: Code added to popular NPM package wiped files in Russia and Belarus
Actually, to my knowledge, I was the very first person to discover the malware contained in the commit range of 847047cf7f81ab08352038b2204f0e7633449580 -> 6e344066a0464814a27fbd7ca8422f473956a803
-
On the Weaponisation of Open Source
From the article:
> I don’t think this can be classed as open source anymore:
> The definition of an Open Source License is quite clear:
> 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons.
> I don’t really want to have to read through each of my dependencies and transitive dependencies licences to determine whether I am agreeing to discriminatory terms by using a library.
I think the author of the article has misunderstood the definition, thus reached the wrong conclusion.
The non-discrimination rule applies only to accessibility and nothing else. Simply put, you provide the same code/product to everybody, including Satan Claus and Mr Putin under the same set of condition and permissions. Adding/removing malicious code does not change the fact that the code is by definition open sourced.
All and all, this is not a license problem.
Now, talk about node-ipc, which just got attacked by mobs (see https://github.com/RIAEvangelist/node-ipc/issues?q=is%3Aissu...).
If an open source project is a scam, then it's a scamware. If an open source project is malicious, then it's a malware.
Personally, as a normal human being, it is hard to keep a peace of mind after watching how the Russians fired multiple heavy rounds to kill the elderly couple who just traveling peacefully in a car down the road near a hospital. It is even harder to keep a peace of mind after watching a video recorded by a son showing how the Russians shoot and killed his father who sits in the driver's seat right beside him. I fully understand and respect the anger.
However, I do agree that people need to be more mature on this even during this difficult time. Turn your project into a malware only hurts your own reputation and people who trusted you. Once the trust is gone, it might never recover. There are many ways to actually hurt those who contributed the invasion. Be constructive and accurate, or at very least don't be destructive.
- Open Source Maintainer Sabotages Code to Wipe Russian, Belarusian Computers
gitian-builder
-
Development roundup for Dogecoin Core - May 14th, 2022
A number of pull requests are still awaiting gitian checks. Unfortunately, my attempt to review and help pulling #2579 (that would make it much easier to do gitian checks) over the finish line, is not ready because the gitian-builder software that we need for this has a bug. I have opened a pull request with them to fix the issue but because Bitcoin Core is moving away from this software, it takes a little longer to get things merged there. If I see no progress on this until Friday the 20th, I will propose to temporarily fix it locally in our own scripts.
- Open Source Maintainer Sabotages Code to Wipe Russian, Belarusian Computers
-
Introduction to my PoW based Cryptocurrency
So I also faced errors even after finding these bad boys. I kept getting a system error but I solved that using help from stack overflow and some Linux forums. Bitcoin.org too was also my close friend. The error was that I haven't started apt-cacher-ng yet. so after solving that I got a new error. With this error it took about three days to find a solution because it was a problem with the code or not with the code but the Ubuntu server location. Ubuntu has moved some archive files from Archive.ubuntu to old-releases.ubuntu. But the gitian builder was still fetching from that place. So as a normal bug solver. I edited the code on GitHub and sent a pull request for DevRandom to review. Guess what MY PULL WAS CORRECT SO HE MERGED ITT!!!! I was soo excited that day that I showed it to all my friends whether they understood or not. I was happy that I had contributed to the software which is literally the backbone of all Altcoins who build through Gitian. I was also happy that I had contributed to the same repository as the names like Gavin Andresen, Luke Dashjr , Hebasto and other prominent developers in the Bitcoin Development community. The link of my two pull request can be found here
-
MWEB Update from Developer David Burkett
The release process we inherited from bitcoin can be quite painful. It uses gitian to build repeatable and deterministic binaries from the source code. This means that multiple people can all build the code on different machines (and even different operating systems) and still get the same exact release binaries. We can then all compare the results and then sign the release, certifying that we all agree that the published release is safe & accurate.
-
Thousands of Debian packages updated from their upstream Git repository
For those interested in reproducible builds, the gitian [1] project is a fairly simple VM which sets the up the necessary environment for doing this sort of thing.
The tooling and community around reproducible builds is growing all the time, and imo we should be insisting on it for things such as government apps.
[1] https://github.com/devrandom/gitian-builder
-
How to verify Dogecoin Core binary releases
git clone https://github.com/devrandom/gitian-builder git clone https://github.com/dogecoin/dogecoin git clone https://github.com/dogecoin/gitian.sigs pushd dogecoin git checkout v1.14.3 popd
What are some alternatives?
vue-cli - 🛠️ webpack-based tooling for Vue.js Development
litecoin
es5-ext - ECMAScript extensions (with respect to upcoming ECMAScript features)
pacman-bintrans - Experimental binary transparency for pacman with sigstore and rekor
peacenotwar - Attempts to determine if the computer its running on has an IP originating from Russia or Belarus. If it is then depending on the version of the malware either attempts to delete all files on the computer, or creates a text file on the computers desktop protesting the war in ukraine.
dogecoin - very currency
Flow.Launcher - :mag: Quick file search & app launcher for Windows with community-made plugins
gitian.sigs - Trusted Build Process signatures
create-vue - 🛠️ The recommended way to start a Vite-powered Vue project
antimony - Antimony is a free open source peer-to-peer electronic cash system that is completely decentralized, without the need for a central server or trusted parties. Users hold the crypto keys to their own money and transact directly with each other, with the help of a P2P network to check for double-spending. Made as a product demo of a blockchain
node-ipc-dependencies-list - List of all dependencies affected by node-ipc malicious commit