![]() ![]() ![]() And second because patching hardware is not as easy, for the manufacturer and for the users or administrators in charge of the systems. They are meaningful for several reasons among them the world wide impact since they affect Intel and AMD systems which are ubiquitous. Spectre and Meltdown are both hardware vulnerabilities. Nowadays it’s a no brainer and operating systems have provided the necessary tools for this to be easy and as smooth as possible. I never planned to do any article on patching anything. It is always a good and I hope a standard practice to have your systems patched and if they aren’t for whatever the reason (that legacy thing you’re carrying on for ages) you may take the necessary extra steps to protect your environment. ![]() # How to mitigate Spectre and Meltdown on an HP Proliant server with FreeBSDĪs recently announced in a previous article I wanted to write a couple of guides on how to mitigate Spectre and Meltdown vulnerabilities in GNU/Linux and UNIX environments. Mitigating Spectre/Meltdown on HP Proliant servers, omniOS installation setup, debugging a memory corruption issue on OpenBSD, CfT for OpenZFS native encryption, Asigra TrueNAS backup appliance shown at VMworld, NetBSD 6 EoL, and more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |