News for hackers. Stuff that matters.
Re:Announcing Rust 1.100.0 by Panzerschrek on Friday November 13, 2026 @12:21AM (#50478693)
> global-min-publish-age = "3 days"

It's not a proper solution. A malicious crate can just contain a time-based switching mechanism in order to be undetected some time (let's say a couple of months) in order to become widespread.

Re:Announcing Rust 1.100.0 by WillDaSilva on Friday November 13, 2026 @12:32AM (#50478773)
There exist companies who scan newly published crates (especially popular ones) for malicious code. Just because the code isn't active yet doesn't mean it won't be caught within a window like this. These measures provide real, albeit imperfect, security.
Re:Announcing Rust 1.100.0 by Panzerschrek on Friday November 13, 2026 @12:37AM (#50478805)
> There exist companies who scan newly published crates

There is only one logical step left - make such scanning mandatory. Even better would be to perform proper audit with real humans involved. In order to cut down costs of such measures, there should be some limit on how often a package may be updated, let's say, once in a week.

Re:Announcing Rust 1.100.0 by nine_k on Friday November 13, 2026 @12:55AM (#50478908)
Isn't it the time between release for analysis and release for use? I suppose that finding malware only when it's activated isn't the only possible way, especially when the complete source code is available.
Re:Announcing Rust 1.100.0 by hmry on Friday November 13, 2026 @07:24AM (#50482518)
This is something I really appreciate about cargo/crates.io's "source code only" distribution, compared to e.g. npm or pip/PyPI.

You always know that the package contents match the source code, and you can always add a dependency by just downloading its source code and putting it into a subdirectory. You don't have to go and set up a different build system for each library if you want to avoid the pre-built artifacts.

Re:Announcing Rust 1.100.0 by woodruffw on Friday November 13, 2026 @07:55AM (#50482831)
People have shipped binaries inside of crates on crates.io. It’s a strong (and good) community convention not to, but there’s nothing stopping it.