Recently Google disclosed a new class of vulnerabilities known as Spectre and Meltdown. Folks in the Decred community have
been asking questions about the implications of these bugs for Decred. This
post delineates implications of these exploits and possible countermeasures.
These bugs are akin to traders issuing cancels without back pressure to
manipulate the market.
Run your wallet on physical hardware you control and DON’T share with others
and DO NOT run a web browser on the same machine. Hardware wallets do not seem
to be affected by these bugs but great care should be taken where they are
Spectre enables memory leakage in a process. That translates to, your
other sensitive information in your web browser over the internet to a third party.
Currently there is no known workaround for this bug and therefore browsers and
internet sites should be considered hostile.
Meltdown enables kernel memory leakage. That translates to: if a third party
has access to the hardware, e.g. a shared cloud machine, one can retrieve
keys/passwords and other sensitive information from memory.
Most operating systems have fixes for this bug. You should update to the
latest operating system version. Do note that your cloud provider may not have
updated the host operating system. Verify this with your host provider.
Decred voting only wallets are less critical because they do not control any
funds. Those can be run in the cloud without risking loss of funds.
It is not always possible to not run a web browser on your wallet machine but
you can mitigate most threats.
The main rules are:
- Update your operating system.
- Update your web browser.
- Disable autofill in your browser.
- Do NOT run a hot wallet on a shared machine or in the cloud.
- Do NOT run a browser on your wallet machine, if possible.
- Do NOT use a hardware wallet on a shared machine.
It is obviously not always possible to not run a web browser on your wallet
machine but there are precautions. For now, only use Firefox and/or Chrome.
- Block ads
- Update your browser. Firefox has mitigation builtin. Chrome requires Strict site isolation
- Disable autofill in your browser
- Start browser with no tabs or sites open before doing any crypto clicking
- Quit browser AFTER completing your crypto clicking.
- Leave browser off unless you need to do anything crypto related (see step 5 and 6).
Those plugins were selected because they exist on Firefox and Chrome. There
are alternatives that will work just as well. The Decred project does not