|
@DogeMocenigo | |||||
|
It is not (only) a (weak) mitigation - it is a tool to discover bugs and vulnerabilities in the field. Testing - including smart fuzzing - does not find all memory access defects. But if MTE information is collected IN THE FIELD you find these defects and with absolute precision
|
||||||
|
||||||
|
John Regehr
@johnregehr
|
19. ruj |
|
memory tagging should be a game changer for C and C++; get with the program, @intel and @apple!! pic.twitter.com/z2vXAtTb7z
|
||
|
||
|
Gok
@Gok
|
19. ruj |
|
I'm going to be that jerkface and predict that MTE won't do all that much. It's a pretty weak mitigation that requires a lot of work to adopt.
|
||
|
|
||
|
|
Gok
@Gok
|
19. ruj |
|
If that was really the goal you could just opportunistically deploy (HW)Asan, which is more precise and doesn’t require replacing billions of devices.
|
||
|
|
||
|
|
The Doge Mocenigo
@DogeMocenigo
|
19. ruj |
|
Replacing? One deploys it on new devices only.
Asan has a huge performance/overhead impact. HWasan’s is still large.
The MTE has a very small impact in memory overhead (IIRC 3-5%) and a similar one in performance.
There is a good reason we chose to do that (and GOOG is onboard).
|
||
|
|
||