Changes

==Security risk==

==Security risk==

In 2018, it was revealed to the public that hyper-threading technology creates an opportunity for a side-channel attack. Because the processor changes state to cycle between threads, there is a possibility that a malicious process running on the processor could access information which it should not be able to. Although such an attack has not yet been seen in the wild, this potentially enables the loss of vital data such as the device's RSA private key.  For this reason, it will probably be phased out, unless it can be altered to maintain process barriers.<ref>https://csdl.computer.org/csdl/proceedings/sp/2018/4353/00/435301a388-abs.html</ref><ref>http://www.daemonology.net/hyperthreading-considered-harmful/</ref><ref>https://thehackernews.com/2018/06/openbsd-hyper-threading.html</ref><ref>https://www.tomshardware.com/news/openbsd-disables-intel-hyper-threading-spectre,37332.html</ref>

In 2018, it was revealed to the public that hyper-threading technology creates an opportunity for a side-channel attack. Because the processor changes state to cycle between threads, there is a possibility that a malicious process running on the processor could access information which it should not be able to. Although such an attack has not yet been seen in the wild, this potentially enables the loss of vital data such as the device's [[RSA]] private key.  For this reason, it will probably be phased out, unless it can be altered to maintain process barriers.<ref>https://csdl.computer.org/csdl/proceedings/sp/2018/4353/00/435301a388-abs.html</ref><ref>http://www.daemonology.net/hyperthreading-considered-harmful/</ref><ref>https://thehackernews.com/2018/06/openbsd-hyper-threading.html</ref><ref>https://www.tomshardware.com/news/openbsd-disables-intel-hyper-threading-spectre,37332.html</ref>

==References==

==References==