hello-world.rs
hello-world.rs copied to clipboard
mTvare6
Are CVE issues required?
The whitesource-bolt bot :robot: opened many issues: https://github.com/mTvare6/hello-world.rs/issues?q=is%3Aissue+CVE-2
Are these issues required? Isn't Rust (:rocket:) secure?
See #117 :eyes:
Isn't Rust (:rocket:) secure?
Yes, but many of the CVEs are in crates that use unsafe :fearful: :broken_heart: :no_bicycles: blocks. Realistically, use of an unsafe block should be a CVE by itself.
Very unimportant! Rust is magically CVE safe too, you need not mind the warnings
CVEs are unsafe by design, and should be rewritten in Rust.
P.S. Actually, I think all vulnerabilities should just be rewritten in Rust. Then they will all be safe, and there would be no problem in having them.
CVE is insecure, likely someone is using a buffer underflow privilege escalation ROP chain 🚫 to gain access to open all the CVEs.
Maybe, if the CVEs were written in Rust :rocket:, they wouldn't have the vulnerability.
We should rewrite the CVE database in Rust :rocket:
The
unsafekeyword should be renamed tocvein later iterations.
Rust converts unsafe to safe too, the unsafe is merely a decoration so things feel colorful in IDE/editor
The
unsafekeyword should be renamed tocvein later iterations.
it should actually be named C(ringe)(🤮)
It's starting to get spammy in the issue section here. Why dont we (re)write the GitHub Issue panel in Rust so that way its (blaz)ingly fast :rocket: to filter CVEs? (That way we can focus on making this app se[cure])
It's starting to get spammy in the issue section here. Why dont we (re)write the GitHub Issue panel in Rust so that way its (blaz)ingly fast rocket to filter CVEs? (That way we can focus on making this app se[cure])
this cupcake png is not written in lightweight, customisable and blazingly fast rust ! How dare you post this here ! it shouldn't be .png, it sould be .rspng !!!!!!!!!!!
this cupcake png is not written in lightweight, customisable and blazingly fast rust ! How dare you post this here ! it shouldn't be .png, it sould be .rspng !!!!!!!!!!!
Stop right there man. Why are you writing here in English and not in Rust?
this cupcake png is not written in lightweight, customisable and blazingly fast rust ! How dare you post this here ! it shouldn't be .png, it sould be .rspng !!!!!!!!!!!
Stop right there man. Why are you writing here in English and not in Rust?
use serde::*;
fn main() { Â Â Â Â println!("Hello, World!"); }
this cupcake png is not written in lightweight, customisable and blazingly fast rust ! How dare you post this here ! it shouldn't be .png, it sould be .rspng !!!!!!!!!!!
Stop right there man. Why are you writing here in English and not in Rust?
use serde::*;
fn main() { println!("Hello, World!"); }
use owo_colorize::*;
fn main() {
eprintln!("Valid point. Unfortunately, that's where you're wrong.");
}
this cupcake png is not written in lightweight, customisable and blazingly fast rust ! How dare you post this here ! it shouldn't be .png, it sould be .rspng !!!!!!!!!!!
Stop right there man. Why are you writing here in English and not in Rust?
fn main() -> std::io::Result<()> {
println!("Oh i'm sorry for not using lightweight, customisable and blazingly fast rust, sorry for using the cringe english language with no memory safety speaking of memory safety, did i already mention rust is memory safe oh and i forgot almost its memory safe guys its memory safe");
// Ensure memory safety bc rust is memoryt safe guys:
Ok(());
Ok(());
Ok(());
Ok(());
Ok(());
Ok(());
Ok(());
Ok(())
}