Creating the World's Safest Devices #EmbeddedRust #UnsafeCode #InterruptDriven #Programming

🔐 Discover why people often get hacked due to poor code in languages like C. Learn how writing safe code in Rust can create the world's safest router and VPN! #coding #rust #safety #security #programming

🔥🔥🔥 SOCIALS 🔥🔥🔥

[arianghorbani]

The people in these comments truly just do not understand the state of codebases globally right now. The Linux kernel hardening project is such a difficult and long-term process because, despite all the clear geniuses in these comments right now who could toootally do work vetting code before it gets into the kernel, tons of insecure code continuously gets in.

It is fundamentally difficult to write secure code in C. That’s not an issue of “knowing what you are doing”. It’s a matter of the millions upon millions of lines of low-level C code that are used in tech that’s bought every day. There WILL be slip-ups, and for every slip-up, a security issue arises which can affect users. Don’t be a selfish developer. recognize the value of a programming language that shifts a significant portion your cognitive load for coding securely onto its own systems.

[lionbryce]

The reason *people* get hacked is usually due to social engineering

[cbjueueiwyru]

I agree but its a dangerous mindset to have the attitude of "its hard to write bad code in rust" and "it's write in rust so its secure"

[YesIndeedIDo]

As a professional python hello world tutorial first step expert I agree.

[rocstar]

I thought the reason ppl get hacked usually is cuz their password are "<name><birthday>" like "john1986"

[Yupppi]

The whole time I was waiting for the punchline where it all explodes or he found a way to break Rust.

[ObiwanNekody]

You should be more clear. It is easy to write poor code in any language. Rust just makes it very difficult to accidentally write code that is in one of the largest categories of exploitable code. It doesn't magically make your code more safe or secure.

[wfekhzg]

I work on embedded systems. C is going no where

[npip]

You could just implement bounds checking in C. C lets you be safe if you want.

Rust doesn't bring anything magical to the table, it immediately wouldn't let you access global data from multiple threads without a lock on the data. You can easily do that in C if you want, it's just slower so that functionality is behind a debug flag.

[Imaginary_One]

The amount of people saying “you just aren’t smart enough to write safe code in C!” and “but Rust is way too hard to learn!” in almost the same breath is quite terrifying.

[colmenasio]

"sir i just asked you what would you like to order"

[AllanSavolainen]

I don't think rust protects you from hacking that much. It can offer some protection against buffer overrun type of attacks, but it doesn't help at all if you make a mistake in authentication or crypto etc.

[travelan]

Its super easy to write rubbish in Rust. Memory safety doesn’t equal no bugs. Id you think not going with C is better because of memory management, then you MUST go with C to learn it. It’s essential to understand and Rust is not the solution.

[FrontierGamers]

As a person who speaks C, I agree we get hacked all the time

[ArachnidAbby]

Memory safety and security arent the same thing.

[fallenflame]

Unfortunately, it's hard to write any code in rust.

[justanaveragebalkan]

That's total bullshit, the reason why people get "hacked" is because they often are too lazy or busy chasing the trend rather than keeping up with latest vulnerabilities that are discovered.

Also lets not pretend that every developers writes https from scratch each time he has to do a post request, to claim security on rust to the extent that it exist in C is borderline false, there are many issues with every niche language.

I use it myself, but i am not delusional enough to claim that it's the holy grail of programming languages, it's a good systems programming language, would not waste time writing anything else.

12 years ago, i had a mentor once ask me after suggesting the new hotness back then.

"Do we launch space ships in the sky?"

"No? Okay, than theoretical advantages don't matter, what does matter is getting paid at the end of the quarter and delivering on our expectations"

Best advice ever.

[quadrupledamage]

It's written in rust, and we've just leaked 2gb of memory on this 128kb ram microcontroller. But hey, memory leaks are inherently safe.

[gerrysweeney]

I think you mean software vulnerabilities are easier to create in C. You will also find that in order for Rust to talk to the hardware (your STM32$xxx there) you will find those parts of your Rust software *must* be in "unsafe mode", so its just as possible to write bad code in those parts.

When you are on bare metal like you are, its much much harder to create a rich application, you have to crank out everything yourself...

[litaxc]

I really want a "safe C" that as safe as Rust, but without the complexity. Zig is so close, but probably not there yet.