To those that are worried about the latest processor vulnerabilities:
1. Ignore ICEBREAKER, his just a troll spreading mischeif and does not know how tech works!
2. Even if its a dedicated / shared vps and it running either linux or windows you will eventually have to update your system to recieve the latest CVE patches.
3. On Linux you would run something like (when the patches are released)
> If you are running Centos / Redhat
Run these commands as the root user or sudo:
"yum update --disableexcludes=all update - y" (without quotes) this will ensure all packages including the kernel are updated even if they are packages defined as exclusions in /etc/yum.conf
> If you are running ubunutu:
"apt-get update" - To get updates
"apt-get upgrade" - To install them
4. For Windows, just go ahead and manually patch it, i am sure Microsoft will be dishing the updates out soon automatically, if you have automated patching runing, you wont see a difference to other updates that you would normally get, but if you patch manually, its best to go ahead and just search for updates ones there released from Microsoft and update.
Doing the above however will mean you have to restart your servers at some point as these are considered kernel patches and only take effect when the devices have been rebooted. Don't worry you wont lose your place on the masternodes so long as your server advertises its a masternode within an hour and you wont need to do a remote restart or anything from the masternode, just start up "dashd" again and you'll be in the payment queue within no time.
Providers such as AWS, Microsoft, Google, Rackspace and other hosting providers etc will all send out communication to those that are effected and give you guidance on how to mitigate and patch anyway so nothing to be worried about.
As mentioned earlier, ignore ICEBREAKER, his a troll! It clearly says it on the left hand side of all my posts just under my profile name
1. Ignore ICEBREAKER, his just a troll spreading mischeif and does not know how tech works!
2. Even if its a dedicated / shared vps and it running either linux or windows you will eventually have to update your system to recieve the latest CVE patches.
3. On Linux you would run something like (when the patches are released)
> If you are running Centos / Redhat
Run these commands as the root user or sudo:
"yum update --disableexcludes=all update - y" (without quotes) this will ensure all packages including the kernel are updated even if they are packages defined as exclusions in /etc/yum.conf
> If you are running ubunutu:
"apt-get update" - To get updates
"apt-get upgrade" - To install them
4. For Windows, just go ahead and manually patch it, i am sure Microsoft will be dishing the updates out soon automatically, if you have automated patching runing, you wont see a difference to other updates that you would normally get, but if you patch manually, its best to go ahead and just search for updates ones there released from Microsoft and update.
Doing the above however will mean you have to restart your servers at some point as these are considered kernel patches and only take effect when the devices have been rebooted. Don't worry you wont lose your place on the masternodes so long as your server advertises its a masternode within an hour and you wont need to do a remote restart or anything from the masternode, just start up "dashd" again and you'll be in the payment queue within no time.
Providers such as AWS, Microsoft, Google, Rackspace and other hosting providers etc will all send out communication to those that are effected and give you guidance on how to mitigate and patch anyway so nothing to be worried about.
As mentioned earlier, ignore ICEBREAKER, his a troll! It clearly says it on the left hand side of all my posts just under my profile name
I don't think you thoroughly comprehend the issue. The vulnerability exists with the hardware, and cannot be fully remediated without hardware replacement. If you believe service providers such as AWS, Azure, etc. can complete the necessary hardware replacement within the next 6 to 12 months, that's naive at best. The replacement is a significant undertaking with extraneous costs, and past the cost factor, hardware vendors cannot even supply at the necessary levels to meet that type of demand. Software vendors will attempt to remediate within their realm/capabilities but each fix will be shortlived as new vulnerabilities are identified within the code identified. Believe me, in the short term, a significant amount effort will be invested in identifying new attack vectors to exploit this persistent vulnerability, by governments and other entities.
This means your coins as the masternode owner may be safe on the VPS or Cloud instance they are hosted on, but the transactions passing through will not be until the underlying hardware is replaced.
On the phone right now writing this, but I fully comprehend the issue and am aware it's hardware related, yes in the short term they can " mitigate " this with software patches which will thus slow down performance, however masternodes are being compensated so they should be able to spec up a beefier server if need be. In the long term yes hardware will need to be replaced, but with digital solutions whether it be on a silicon chip or even software based there will always be flaws, bugs etc discovered, that's just a apart of life, after all its humans who are behind the tech and we all make mistakes
unless ur ICEBREAKER of course.. Hehe his perfect! Sykes. 
) copy and paste posts.
