| |
| Posted by Steven Schveighoffer in reply to Johan | PermalinkReply |
|
Steven Schveighoffer
| On 12/2/21 7:15 AM, Johan wrote:
> On Thursday, 2 December 2021 at 11:01:07 UTC, Imperatorn wrote:
> On Thursday, 2 December 2021 at 08:09:18 UTC, Paulo Pinto wrote:
> Google's Project Zero goes through a memory corruption exploit on Network Security Services, where despite all static analysers, fuzzers and code reviews, it flew under the radar.
https://googleprojectzero.blogspot.com/2021/12/this-shouldnt-have-happened.html
Hence why @safe matters.
Bottom line:
Use D instead of C 😎
Sorry to rain on the party here, but D is of course not at all immune to this problem.
It was not hard to find out-of-bounds memory access in the D compiler, using the fuzz techniques mentioned in the article.
The D compiler is not @safe.
Using D isn't enough, you need to use @safe D.
Even that isn't enough, because most of the time people misuse @trusted (because it's so easy to misuse).
-Steve
|