Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

I don't really understand why this doesn't cover memory safety.


sort by: page size:

Isn't this confusing memory safety with safety?

I'm not sure you understand what "memory safety" means.

I see no mention of memory safety or unsafety in the issue you linked. Could you be more specific?

That's not what memory safety refers to.

Memory safety?

OTOH, we don't really have evidence to show that memory safety is effective in kernels/drivers because no memory safe language has ever been deployed at scale for that purpose.

This is incorrect. What you're referring to is "memory safety".

its “memory safety”, not “accesses memory”

> without any memory safety

Actually, I think that would be memory protection, not safety.


It still lacks memory safety.

The point is that not every security problem stems from the memory model, and myopically focusing on memory safety evidently doesn't stop do much to prevent vulnerabilities.

Oh right, good point. Other types of memory safety are more relevant here then.

It has everything to do with memory safety.

One catch is that it's not currently memory safe, and it's unclear (to me) what the future plan is for memory safety.

So then memory safety isn't the end-all be-all for security anyways. What do you suggest we use instead?

This is getting a bit defensive. I think people are interpreting your post as saying all safety is guaranteed by using memory safety, but you rightly walk it back in comments to mean it addresses "primary" security problems.

That's it.


Interesting, I hadn’t realized how much the phrase “memory safety” understates what is desirable.

Those don’t really catch memory safety issues in the general case; they’re more focused on exploit mitigation.

So memory safety is a cons point now?
next

Legal | privacy