mirror of
				https://github.com/privacyguides/privacyguides.org.git
				synced 2025-10-31 03:26:35 +00:00 
			
		
		
		
	operating-systems.html: add a warning for Linux/CPU vulns (#1231)
* operating-systemd.html: add a warning for Linux/CPU vulns * operating-systems: expand the Linux instructions for MDS mitigation * operating-systems: s/multithreading/hyperthreading/ * operating-systems: address feedback, fix typo * operating-systems: remove update-grub, close li tags * operating-systems: @nitrohorse's first feedback Doing this in a separate commit in case I misunderstood, so I can revert * operating-systems: address feedback * operating-systems: dd a duplicate paragraph * operating-systems: add missing "grub" word * operating-systems: fix the last step of nosmt * operating-systems: mention macOS link * operating-systems: address feedback * operating-systems: add a dot * operating-systems: fix link
This commit is contained in:
		 Mikaela Suomalainen
					Mikaela Suomalainen
				
			
				
					committed by
					
						 nitrohorse
						nitrohorse
					
				
			
			
				
	
			
			
			 nitrohorse
						nitrohorse
					
				
			
						parent
						
							a88adcc3bf
						
					
				
				
					commit
					0276f52ed2
				
			| @@ -41,6 +41,33 @@ tor="http://sejnfjrq6szgca7v.onion" | ||||
|   <li><a href="#win10"><i class="fas fa-link"></i> Don't use Windows 10 - It's a privacy nightmare</a></li> | ||||
| </ul> | ||||
|  | ||||
| <h4 id="cpuvulns">Remember to check CPU vulnerability mitigations</h4> | ||||
|  | ||||
| <p><em><a href="https://support.microsoft.com/en-us/help/4073757/protect-windows-devices-from-speculative-execution-side-channel-attack">This also affects Windows 10</a>, but it doesn't expose this information or mitigation instructions as easily. MacOS users check <a href="https://support.apple.com/en-us/HT210108">How to enable full mitigation for Microarchitectural Data Sampling (MDS) vulnerabilities on Apple Support</a>.</em></p> | ||||
|  | ||||
| <p>When running a enough recent kernel, you can check the CPU vulnerabilities it detects by <code>tail -n +1 /sys/devices/system/cpu/vulnerabilities/*</code>. By using <code>tail -n +1</code> instead of <code>cat</code>, the file names are also visible.</p> | ||||
|  | ||||
| <p> | ||||
|     In case you have an Intel CPU, you may notice "SMT vulnerable" display after running the <code>tail</code> command. To mitigate this, disable <a href="https://en.wikipedia.org/wiki/Hyper-threading">hyper-threading</a> from the UEFI/BIOS. You can also take the following mitigation steps below if your system/distribution uses GRUB and supports <code>/etc/default/grub.d/</code>: | ||||
| </p> | ||||
|  | ||||
| <ol> | ||||
|   <li><code>sudo mkdir /etc/default/grub.d/</code> to create a directory for additional grub configuration</li> | ||||
|   <li><code>echo GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT mds=full,nosmt" | sudo tee /etc/default/grub.d/mds.conf</code> to create a new grub config file source with the echoed content</li> | ||||
|   <li><code>sudo grub-mkconfig -o /boot/grub/grub.cfg</code> to generate a new grub config file including this new kernel boot flag</li> | ||||
|   <li><code>sudo reboot</code> to reboot</li> | ||||
|   <li>after the reboot, check <code>tail -n +1 /sys/devices/system/cpu/vulnerabilities/*</code> again to see that MDS now says "SMT disabled."</li> | ||||
| </ol> | ||||
|  | ||||
| <h5>Further reading</h5> | ||||
|  | ||||
| <ul> | ||||
|   <li><a href="https://cpu.fail/">CPU.fail</a></li> | ||||
|   <li><a href="https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html">MDS - Microarchitectural Data Sampling on The Linux kernel user's and administrator's guide</a></li> | ||||
|   <li><a href="https://mdsattacks.com/">RIDL and Fallout: MDS attacks on mdsattacks.com</a></li> | ||||
|   <li><a href="https://en.wikipedia.org/wiki/Simultaneous_multithreading">Simultaneous multithreading on Wikipedia</a></li> | ||||
| </ul> | ||||
|  | ||||
| <h3>Worth Mentioning</h3> | ||||
|  | ||||
| <ul> | ||||
|   | ||||
		Reference in New Issue
	
	Block a user