3 ms·
If you are trying to prevent attacker code communicating with another piece of attacker code on another core: No. It isn't secure. There are a lot of side c
by londons_explore 5y ago
If you are trying to prevent attacker code communicating with another piece of attacker code on another core: No. It isn't secure. There are a lot of side channels.
If you are trying to prevent attacker code figuring out what code is running on another core: No. Patterns of L3 cache eviction and memory bus contention will probably leak sufficient information to have a good guess what another core is up to.
If you are trying to prevent attacker code figuring out data in another cores memory or registers: Probably, yes. As long as the core is doing something with no data dependent branches, or instructions with data dependent timings, it should be safe.
Very little code is written to have no data dependent branches, or instructions with data dependent timings. Some well written cryptography code has that, but thats about it.
- omegalulw 5y ago> Very little code is written to have no data dependent branches, or instructions with data dependent timings Ooh I have some idea on how to use data dependent branches in your own code to leak critical information through side channels (Spectre) but how do you leak information from others' data dependent branches and instructions?
- londons_explore 5y agoImagine code you want to attack has an array lookup based on some secret data: x = array[secretdata]. The entry in the array will be loaded into the cpu core via the L3 cache. If the L3 cache is already full, then one entry will have to be evicted from the cache. The evicted entry will depend on the memory address that is being accessed. Another CPU, running an attackers code, can repeatedly try to load stuff from L3, and detect what was evicted and when to learn the secretdata.