Re:LogoFAIL: Secure Boot bypass with manipulated boot logos
by stefan_ on Wednesday December 06, 2023 @02:35PM
(#38548438)
While Apple will spend billions on the latest techniques to ensure your iPhone can only run things Apple signed, there is meanwhile a real lack of enthusiasm around the basics like making the central messaging app not a native code shitshow invoking obscure (native of course) open source libraries they never update, you know, the basics. It's the latter that keeps getting their customers exploited.
Re:LogoFAIL: Secure Boot bypass with manipulated boot logos
by hug on Wednesday December 06, 2023 @05:53PM
(#38550612)
Why are you emphasising native code? Is there something about native code being bad that I am missing?
Re:LogoFAIL: Secure Boot bypass with manipulated boot logos
by geraldhh on Thursday December 07, 2023 @03:47AM
(#38554282)
everything not running in a browser is bad, b/c it's not within reach of the fullstack shitheads /s
Re:LogoFAIL: Secure Boot bypass with manipulated boot logos
by xerox13ster on Thursday December 07, 2023 @09:39AM
(#38556827)
if they can't go down to the metal, they're not "fullstack" /s
Re:LogoFAIL: Secure Boot bypass with manipulated boot logos
by chriswarbo on Thursday December 07, 2023 @09:02AM
(#38556410)
Native code has more direct access to the system, e.g. accessing arbitrary regions of a process's memory via pointer arithmetic, invoking arbitrary syscalls, etc. In contrast, "managed code" like a JVM, CPython VM, etc. is subject to a more structured semantic model, which allows more restrictions to be imposed.
Don’t blame shoddy implementations by companies who are only checking checkboxes.