Kernel buffer overflow exposes iPhone 11 Pro to radio based attacks

[Paul Backus]

On Wednesday, 9 December 2020 at 08:29:58 UTC, Bruce Carneal 
wrote:
>
> IIUC, such functions in existing .o files and libs would not be 
> designated (mangled) @safe so I'd expect linker errors, not 
> silence.  New compilations will have the source body and will, 
> of course, reject non @safe code so, again, not silent. What 
> have I misunderstood?  What is the "silent" problem?  Is there 
> some transitive issue?
>
> Note: @safe designation should be part of the external mangle 
> of any future defaulted-and-verified- at safe function.  I don't 
> see how it works otherwise.

This does not work for extern(C) functions because their names 
are not mangled.