Xeno Kovah on Nostr: nprofile1q…kg90f nprofile1q…mdexn I was addressing the research in the context in ...

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq6tx08mwy9vkkjen5s8ahy9e3x5z4dmykefvs7u6wex0s02puuskq6kg90f (nprofile…g90f) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq47653442ud3e8z3l8c9zuz9m548pv0mxcwfn28d49fdkdyqx8sdqlmdexn (nprofile…dexn) I was addressing the research in the context in which it was given. I’m aware that chips can have varying architectures (attached but non-animated examples from future class), and that a HCI-using architecture is not necessarily the most likely in the case of the ESP32. And indeed given that the research focused on IoT devices in the last few slides, it seems like the least likely place for HCI to matter in some sense. But I didn’t want to muddy the water with speculation, and I have no direct knowledge of population distribution of different architectures in the ESP32-specific ecosystem. So it’s basically “OK, if they want to talk about a vulnerability under the assumption of HCI, let’s talk about it under that assumption”.