Re: What I've Learned About Rust: 7/2/2025 7pm Eastern Standard time

On 7/2/25 08:18, Sarah Newman wrote:
> On 7/2/25 00:14, Steve Litt wrote:
>> You need to try really hard to write insecure code in Rust.
> 
> I would say there are plenty of opportunities to write insecure code in 
> rust running on Linux if you don't know how Linux (or a lot of other 
> components) work too.

It's to the point where the people who cover security exploits need the 
standard "Would Rust have fixed this? Well, no..." section at the end:

https://youtu.be/9CISphpvapI

>> Like all safety first languages (Ada for instance), the compiler gets
>> in your way a lot, and when you're at my stage it's frustrating. But
>> it's nice that nobody's going to buffer-overrun my Rust code.

Or presumably C code built using the address sanitizer in current llvm 
and gcc toolchains (-fsanitize=address and libasan).

>> * Enough material to learn via ChatGPT and web searches

You want to write safer code by involving ChatGPT.

Well that's certainly a point of view.

Rob