diff options
| author | Franciosi <andre@franciosi.org> | 2022-08-09 21:20:21 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-09 21:20:21 -0300 |
| commit | 085f11a3cc0b744980fc9f72d8ec0f265d99d7f1 (patch) | |
| tree | 20a8a1c31fc808ca940644af8ba760821084f297 | |
| parent | Merge pull request #311 from michael-k/typo (diff) | |
| download | YubiKey-Guide-085f11a3cc0b744980fc9f72d8ec0f265d99d7f1.tar.gz | |
Quick VMware name correction
s/VMWare/VMware
| -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)) |