* Posts by Traveller from the outer rim

3 publicly visible posts • joined 30 Oct 2019

Running on Intel? If you want security, disable hyper-threading, says Linux kernel maintainer

Traveller from the outer rim

Re: Same process = no problem @Traveller

I think the issue that your are touching is much broader. If you host a service (e.g. a web browser) that expose a Turing machine (e.g. a javascript engine) to external parties (e.g. websites), then you need to be very careful about what is available to that Turing machine. Ensuring that code is not able to exploit speculative execution bugs in that closed environment should be easy (and to my understanding it has been solved).

With regards to scheduling, then it would be similar to being NUMA-aware when scheduling.

Traveller from the outer rim

Re: Quick question

This is not a lot harder than exploiting buffer overruns. You still need to understand the code and memory space of the process you are trying to attack. The cool thing with this is that you can do it without anyone noticing it ...

Traveller from the outer rim

Same process = no problem

If two threads from the same process shares a core, then there is no problem. Hyperthreading only becomes a problem when threads from different processes shares a core. Thus, the kernel should allow hyperthreading within a process.