peacenotwar
cargo-crev
Our great sponsors
peacenotwar | cargo-crev | |
---|---|---|
33 | 55 | |
155 | 2,034 | |
- | 2.4% | |
7.0 | 7.7 | |
over 1 year ago | 25 days ago | |
JavaScript | Rust | |
GNU General Public License v3.0 only | Apache License 2.0 |
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.
peacenotwar
-
Open Source Hacktivism, Open Source Gains Traction in the Enterprise, and More: Open Source Matters
Today, with an ongoing war between Russia and Ukraine, some open source maintainers have taken it upon themselves to protest the war via changes to their code that express anti-war rhetoric via messages that display when the software is run. However, one maintainer in particular took it to the next level. Brandon Nozaki Miller, published a library on GitHub named peacenotwar that simply printed an anti-war message to the computer it was run on. This package is harmless on its own, but things got interesting when he included this package as a dependency in the node-ipc module he maintains. Users who downloaded the latest version of node-ipc to a machine in Russia would be subject to complete data destruction. Miller defended the act by claiming that this is all documented publicly and that users who don’t want this installed on their machine should lock their dependencies to older versions.
-
node-ipc go brrrr
apparently an NGO working in belarus got affected
-
American NGO using node-ipc lost 30k files detailing war crimes
From that reddit thread, here is the github issue the paste originated from.
https://github.com/RIAEvangelist/peacenotwar/issues/45
-
Human Rights Organization in Ukraine was the victim of a malware attack by an "activist" targeting Russian and Belorusian IPs
the repo where this issue was posted simply created a .txt file on the user's machine, doesn't wipe anything: https://github.com/RIAEvangelist/peacenotwar/issues/45
-
Open Source Maintainer Sabotages Code to Wipe Russian, Belarusian Computers
This headline is fucking yikes, the node package that they're talking about is fully open source and does nothing but make a text file in 3 locations. It does nothing remotely close to "wiping" computers, lmfao.
-
BIG sabotage: Famous npm package (node-ipc) deletes files to protest Ukraine war
His actions destroyed over 30,000 messages & files detailing war crimes committed by Russian in Ukraine belonging an American NGO that monitors human rights infringements in eastern Europe. Cool protest, bro.
-
Un paquet npm compromis par l'auteur efface les fichiers sur les ordinateurs russes et biélorusses lors de l'installation, pour protester contre l'invasion de l'Ukraine par la Russie
Première victime collatérale
-
Developers of node-ipc edited the software so that anyone with a russian or belarusian IP would get their drive scrubbed clean of data, drama ensues.
Links to drama: https://github.com/RIAEvangelist/peacenotwar/issues, https://github.com/RIAEvangelist/node-ipc/issues
-
My entire PC got wiped Do not download
The package uses https://github.com/RIAEvangelist/peacenotwar to deliver the message.
But I don't understand why/how it would wipe the PC. Unless I missed something, the code from the package does not delete anything.
> This code serves as a non-destructive example of why controlling your node modules is important. It also serves as a non-violent protest against Russia's aggression that threatens the world right now.
Nah, the author knew it's would be controversial. The first sentence is there as an excuse.
- Node-ipc supply chain attack: peacenotwar
cargo-crev
-
Hard disk LEDs and noisy machines
In other cases it may be more documented, such as Golangs baked-in telemetry.
There should be better ways to check these problems. The best I have found so far is Crev https://github.com/crev-dev/crev/. It's most used implementation is Cargo-crev https://github.com/crev-dev/cargo-crev, but hopefully it will become more required to use these types of tools. Certainty and metrics about how many eyes have been on a particular script, and what expertise they have would be a huge win for software.
-
Rust Without Crates.io
The main problem the author is talking about is actually about version updates, which in Maven as well as crates.io is up to each lib's author, and is not curated in any way.
There's no technical solution to that, really. Do you think Nexus Firewall can pick up every exploit, or even most? How confident of that are you, and what data do you have to back that up? I don't have any myself, but would not be surprised at all if "hackers" can easily work around their scanning.
However, I don't have a better approach than using scanning tools like Nexus, or as the author proposes, use a curated library repository like Debian is doing (which hopefully gets enough eyeballs to remain secure) or the https://github.com/crev-dev/cargo-crev project (manually reviewed code) also mentioned. It's interesting that they mention C/C++ just rely on distros providing dynamic libs instead which means you don't even control your dependencies versions, some distro does (how reliable is the distro?)... I wonder if that could work for other languages or if it's just as painful as it looks in the C world.
-
I don't care about cookies” extension bought by Avast, users jump ship
For instance, the worst company imaginable may be in charge of software that was once FOSS, and they may change absolutely nothing about it, so it should be fine. However, if a small update is added that does something bad, you should know about it immediately.
The solution seems to be much more clearly in the realm of things like crev: https://github.com/crev-dev/cargo-crev/
Wherein users can get a clear picture of what dependencies are used in the full chain, and how they have been independently reviewed for security and privacy. That's the real solution for the future. A quick score that is available upon display everytime you upgrade, with large warnings for anything above a certain threshold.
-
I think there should be some type of crates vertification especially the popular ones?
The metrics on crates.io are a useful sniff test, but ultimately you need to review things yourself, or trust some contributors and reviewers. Some projects, like cargo crev or cargo vet can help with the process.
-
[Discussion] What crates would you like to see?
You can use cargo-geiger or cargo-crev to check for whether people you trusted (e.g. u/jonhoo ) trust this crate.
-
Pip and cargo are not the same
There is a similar idea being explored with https://github.com/crev-dev/cargo-crev - you trust a reviewer who reviews crates for trustworthiness, as well as other reviewers.
- greater supply chain attack risk due to large dependency trees?
-
Why so many basic features are not part of the standard library?
[cargo-crev](https://github.com/crev-dev/cargo-crev) looks like a good step in the right direction but not really commonly used.
-
“You meant to install ripgrep”
'cargo crev' makes this kind of workflow possible: https://github.com/crev-dev/cargo-crev
-
Difference between cargo-vet and cargo-crev?
The crev folks themselves are no fans of PGP but need a way to security identify that you are in fact the review author, so that's where the id generation comes in. Ultimately crev is just a bunch of repos with text files you sign with IDs. The nice property is that you can chain these together into a web of trust and it's unfortunate that vet doesn't just use the same signed files on repos model as a foundation because even if they don't trust anyone else, we could turn around and trust them.
What are some alternatives?
node-ipc - A nodejs module for local and remote Inter Process Communication (IPC), Neural Networking, and able to facilitate machine learning.
crates.io - The Rust package registry
es5-ext - ECMAScript extensions (with respect to upcoming ECMAScript features)
stackage - Stable Haskell package sets: vetted consistent packages from Hackage
vue-cli - 🛠️ webpack-based tooling for Vue.js Development
crates.io-index - Registry index for crates.io
protestware-list
serde - Serialization framework for Rust
npm
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project
tiny-http - Low level HTTP server library in Rust
Rustup - The Rust toolchain installer