Kernel buffer overflow exposes iPhone 11 Pro to radio based attacks

[Testle]

On Thursday, 3 December 2020 at 10:36:45 UTC, Paulo Pinto wrote:
> On Thursday, 3 December 2020 at 10:12:35 UTC, Max Haughton 
> wrote:
>> On Thursday, 3 December 2020 at 10:07:19 UTC, IGotD- wrote:
>>> On Thursday, 3 December 2020 at 09:04:56 UTC, Paulo Pinto 
>>> wrote:
>>>>
>>>> F-Secure apparently is living in a phantasy world, 
>>>> https://www.f-secure.com/en/consulting/foundry/usb-armory
>>>
>>> How does this product has to do with safe and unsafe language 
>>> designs?
>
>
> The whole software stack is 100% written in TamaGo (bare metal 
> Go for ARM SoCs), which obviously you didn't bother to read 
> about on the product page.


It is also severally limited. It looks like it is designed to be 
used for purpose built tasks, not as a general use operating 
system. It works because all the complexity of an OS like Linux 
isn't implemented at all. This is done intentionally. You are 
comparing apples to oranges and then saying you dont understand 
why the people talking about apples don't like your oranges.

I don't think any amount of reboot of D will make it more popular 
with people that are flocking to Rust. D proposed a system that 
didn't get traction, another language came along proposed 
something different and did get traction. There are many problems 
with D as it stands, I use it for smaller hobby projects but it 
would be a nightmare to use in a larger project that needs to be 
maintained. Part of that problem is with how the project is 
managed. Sure everyone has their own opinions of this, and that's 
one of the reasons that gets brought up about problem. Problems 
users face aren't taken seriously, it seems management is more 
concerned with follow trends like implementing borrow ownership 
than addressing actual problems have brought up. The @safe by 
default is a good example of that. Rather than listening to the 
outcry from the community to change one thing, the entire thing 
was just shut down.