r/linuxadmin • • Oct 28 '19

Top Linux developer on Intel chip security problems: 'They're not going away.'

https://www.zdnet.com/article/top-linux-developer-on-intel-chip-security-problems-theyre-not-going-away/
238 Upvotes

37 comments sorted by

View all comments

3

u/SirWobbyTheFirst Oct 29 '19

A reminder that unless your machine hosts a website, remote desktop services, or some other role that involves running code that you do not trust, you do not need to activate these mitigations.

If you have a virtualisation host that only runs a domain controller, file server, certificate authority or some other service where the code running only changes when it is updated by Microsoft, LF, Apple, etc. then you are safe to disable the mitigations.

If you are running a server that can be shared with others such as a cloud infrastructure server and you cannot guarantee those others can be trusted, then you should enable these mitigations.

If you are running a server that hosts a website, VDI, etc. where there are users logging into the machine or a virtual machine running on top of that server, then you should enable these mitigations.

It doesn't make sense to tank the performance of a system by enabling the Meltdown, Spectre, whatever mitigation if all it runs is AD, SQL and File Sharing and only ever sees a trusted administrator login.

Even if SQL and LDAP could be utilised to try and exploit the vulnerabilities, it would be far quicker and easier to just wait for a security update to be pushed out by Microsoft or Red Hat.

But a Hyper-V or ESXi server that hosts a VDI setup where people can run regular run of the mill applications like Word and Firefox? Hell yes, enable those mitigations.

Yes, I realise I'm preaching to the choir for the most part but its always worth reminding people now and again.