Kernel buffer overflow exposes iPhone 11 Pro to radio based attacks
Paul Backus
snarwin at gmail.com
Wed Dec 9 14:05:44 UTC 2020
On Wednesday, 9 December 2020 at 11:46:41 UTC, Dukc wrote:
>
> It might have some benefit: If non-annotated C libraries are
> considered `@safe`, it'll mean that not-so-quality code is
> using compromised `@safe`. Bad. But if they are considered
> `@system`, not-so-quality code will not be using `@safe` AT
> ALL. Even worse.
Using compromised @safe is much, much worse than not using @safe
at all. Not using @safe at all means you still have the option of
migrating to @safe in the future. If you're using compromised
@safe, you have no migration path.
More information about the Digitalmars-d
mailing list