by kingsleyopara on 3/21/24, 2:51 PM with 92 comments
by jerf on 3/21/24, 4:37 PM
This is the sort of thing that would metaphorically drive me to drink if I were implementing crypto code. It's an uphill battle at the best of times, but even if I finally get it all right, there's dozens of processor features both current and future ready to blow my code up at any time.
by xiconfjs on 3/21/24, 4:53 PM
by theobservor on 3/21/24, 4:44 PM
As long as these effects cannot be exploited remotely, it's not a concern. Of course multi-tenant cloud-based virtualization would be a no go.
by saagarjha on 3/21/24, 8:35 PM
> Yes, but only on some processors. We observe that the DIT bit set on m3 CPUs effectively disables the DMP. This is not the case for the m1 and m2.
Surely there is a chicken bit somewhere to do this?
by john_alan on 3/21/24, 8:24 PM
Also looks like they need to predetermine aspects of the key.
Very cool but I don’t think it looks particularly practical.
by woadwarrior01 on 3/21/24, 3:56 PM
by 0xedd on 3/22/24, 1:18 PM
by olliej on 3/22/24, 4:36 PM
https://developer.apple.com/documentation/xcode/writing-arm6...
by slowmovintarget on 3/23/24, 5:09 PM
(Compromise must be running on the same hardware.)
by Shtirlic on 3/21/24, 9:16 PM
by d-z-m on 3/22/24, 2:52 AM
by martinky24 on 3/21/24, 4:08 PM