As always, you can sign up for our security announcements mailing list. It’s only posted to when there is a security announcement.https://groups.google.com/forum/m/#!forum/rustlang-security-announcements …
-
-
Prikaži ovu nit
-
We’ve published 1.29.1 with a fix for the str::repeat issuehttps://blog.rust-lang.org/2018/09/25/Rust-1.29.1.html …
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
Tweet je nedostupan.
-
Currently, we only support the latest stable. We may make exceptions in extremely serious cases; this isn’t one of them.
- Još 2 druga odgovora
-
-
-
Is there a warning in cargo, so that if you would use a vulnerable rust version it warns you that you have to update rust + recompile your code, if you're affected?
-
There is not; we don’t have any infrastructure for that kind of thing.
Kraj razgovora
Novi razgovor -
-
-
isn't it slice::repeat though?
-
This is a good point; it’s both
- Još 1 odgovor
Novi razgovor -
-
-
"If you are not using str::repeat, you are not affected." That's not fully true, though. If any of the dependencies of my crate uses the function, my crate is affected. And since it's std lib, it's not easy to look at my crate's deps and tell if it's used it not. Right?
-
Cargo vendor + ripgrep
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.