Live data from Hacker News

Incident Report: CVE-2024-YIKES

nesbitt.io

41–50 of 187 posts

Re: Incident Report: CVE-2024-YIKES

#41
post #36

Earlier quoted context omitted.

In any case, not really a hacker's creed. This has always been withinin the realm of corporations, especially Silicon Valley or adjacent.

MFABT is about survival. Don't hate the player, hate the game.

I'm not sure what you're responding to.

Re: Incident Report: CVE-2024-YIKES

#42
imagine a future where white-hat vs black-hat "AI" go around the web trying to patch vs exploit 0-days

and then become aware of each other

and then try to eliminate each other for decades

each escalating resource capture and writing new generations of better "AI"

Re: Incident Report: CVE-2024-YIKES

#43
post #35
post #11

Customers give us heat for not shipping the latest vulpine-lz4. Their AI-based heuristic antivirus total defence solution automatically flags all software not running latest versions of everything Kindly advice

Ya, latest is a mess. I don't care about latest, I want the version with no known security flaws.

Latest has no known security flaws.

Re: Incident Report: CVE-2024-YIKES

#45

Earlier quoted context omitted.

Move high value crates into the standard library?

This bloats the std library and forces lots more work and stress on the rust dev team. Not to mention it’ll add more churn to the std lib.

One man's bloat is another man's batteries-included, I guess?

My argument would be that if a more featureful standard library could get Rust closer to the superior dependency culture of Go, it'd be worth it. As-is, Rust dependency trees are just wild.

Re: Incident Report: CVE-2024-YIKES

#46
> Day 1, 14:47 UTC — Among the exfiltrated credentials: the maintainer of vulpine-lz4, a Rust library for “blazingly fast Firefox-themed LZ4 decompression.” The library’s logo is a cartoon fox with sunglasses. It has 12 stars on GitHub but is a transitive dependency of cargo itself.

I got a bit curious and here is an incomplete list of crates to compromise to be part of the cargo build and that already have a build.rs so it doesn't stand out to much:

flate2 tar curl-sys libgit2-sys openssl-sys libsqlite3-sys blake3 libz-sys zstd-sys cc

As a nice bonus - if you get rights for xz2 you can compromise rustup.

Fwiw at least they do track Cargo.lock

Re: Incident Report: CVE-2024-YIKES

#47
post #4
post #2

Supply chain incidents suck and we need to do better. Personally for rust I’m a proponent of the foundation supporting a few core crates that go under the same audit procedure as the main rust language and give funding to the project to limit supply chain vulns. I don’t think the right answer is to remove systems like crates or npm. Crate and npm are a boon for many developers.

do we really need both npm and nmp though

and pnpm

Re: Incident Report: CVE-2024-YIKES

#49
post #36

Earlier quoted context omitted.

In any case, not really a hacker's creed. This has always been withinin the realm of corporations, especially Silicon Valley or adjacent.

MFABT is about survival. Don't hate the player, hate the game.

Por que no los dos? Some players seem very gleeful.

Re: Incident Report: CVE-2024-YIKES

#50

For anyone confused, this is (very good imo) fiction about supply-chain incidents. It had me very worried during a brief scan that it was real though, which made me read it more attentively :)

I couldn't tell at first, tbh. It had this vibe: https://github.com/bitcoin/bips/blob/master/bip-0042.mediawi...
Post reply on HN