diff options
author | drduh <github@duh.to> | 2022-08-21 11:23:37 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-08-21 11:23:37 -0700 |
commit | 8f2cd81a9fa54bc96643b2ac36271b4d822dca51 (patch) | |
tree | 56f9b999faf9c75c97c576108ba16a8551a18aa2 | |
parent | Merge pull request #339 from fkr/master (diff) | |
parent | Quick VMware name correction (diff) | |
download | YubiKey-Guide-8f2cd81a9fa54bc96643b2ac36271b4d822dca51.tar.gz |
Merge pull request #338 from franciosi/patch-1
Quick VMware Name Correction
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -102,7 +102,7 @@ You will also need several small storage devices (microSD cards work well) for s To create cryptographic keys, a secure environment that can be reasonably assured to be free of adversarial control is recommended. Here is a general ranking of environments most to least likely to be compromised: 1. Daily-use operating system -1. Virtual machine on daily-use host OS (using [virt-manager](https://virt-manager.org/), VirtualBox, or VMWare) +1. Virtual machine on daily-use host OS (using [virt-manager](https://virt-manager.org/), VirtualBox, or VMware) 1. Separate hardened [Debian](https://www.debian.org/) or [OpenBSD](https://www.openbsd.org/) installation which can be dual booted 1. Live image, such as [Debian Live](https://www.debian.org/CD/live/) or [Tails](https://tails.boum.org/index.en.html) 1. Secure hardware/firmware ([Coreboot](https://www.coreboot.org/), [Intel ME removed](https://github.com/corna/me_cleaner)) |