Are CVE issues required?

[alexislefebvre]

The whitesource-bolt bot 🤖 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 👀

[jagerman]

Isn't Rust (:rocket:) secure?

Yes, but many of the CVEs are in crates that use unsafe 😨 💔 🚳 blocks. Realistically, use of an unsafe block should be a CVE by itself.

[mTvare6]

Very unimportant! Rust is magically CVE safe too, you need not mind the warnings

[alexislefebvre]

Right, thanks.

[alexislefebvre]

I closed this issue because you answered it.

[WilliamVenner]

Thank you for your contribution!

[AlexAT]

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.

[tripulse]

The unsafe keyword should be renamed to cve in later iterations.

[LoganDark]

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 🚀, they wouldn't have the vulnerability.

We should rewrite the CVE database in Rust 🚀

[mTvare6]

The unsafe keyword should be renamed to cve in later iterations.

Rust converts unsafe to safe too, the unsafe is merely a decoration so things feel colorful in IDE/editor

[TruncatedDinoSour]

dw they're memory safe

[TruncatedDinoSour]

The unsafe keyword should be renamed to cve in later iterations.

it should actually be named C(ringe)(🤮)

[LeoDog896]

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 🚀 to filter CVEs? (That way we can focus on making this app se[cure])

[TruncatedDinoSour]

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 !!!!!!!!!!!

[AlexAT]

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?

[LoganDark]

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!");
}

[LeoDog896]

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.");
}

[TruncatedDinoSour]

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(())
}

[TruncatedDinoSour]

use *::*; // Ensures that rust is memory safe

fn main() { // memory safety guys
    println!("Hello, I just found out GitHub isn't running customisable, lightweight and blazingly fast rust and it's running gross, unsafe and slow JS, I think we should abandon github and move to reduxOS and use ssh between reduxOS machines because rust is memory safe oh did I also mention that rust is memory safe ? rust is memory safe I think we should use rust memory safety guys memory safe !!! Also I think we should abandon the rust compiler as it uses unsafe blocks and uses memory, meaning it's not memory safety, memory safety guys"); // more memory safety
    // memory safety
} // memory safety

// memory safety:
// mamory-safety memory-safe safety memory-safe main.memory-safe -memory-safe-out memory-safe

[slbsh]

use *::*; // memry safety memorysafetuy memory safe

unsafe { // Here we make sure that we have memory safety safe memory safe 
    fn memory_safety() -> std::io::Result<()> {
        println!("agreed memory save blazing fasttt rusttt code momory sa");
        Ok(()); // memory safety
        Ok(()) 
    }

    fn main() {
        memory_safety() //memory safety
    }
}

[pushbytes]

Actually I only do nodejs plus cee puls lupsl 🤓
rust so slow >:((((((((

asm > rust
binary is winning