From 5b70ada5d95464078f8157a1568a4a7fbe9311c9 Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Tue, 27 Mar 2018 14:58:13 -0700 Subject: [PATCH 1/2] Update installation.html.md --- .../source/docs/vmware/installation.html.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/website/source/docs/vmware/installation.html.md b/website/source/docs/vmware/installation.html.md index 37e684e00..16e0ffab6 100644 --- a/website/source/docs/vmware/installation.html.md +++ b/website/source/docs/vmware/installation.html.md @@ -61,6 +61,31 @@ $ vagrant If the license is not installed correctly, you will see an error message. +## Upgrading to v1.x + +It is **extremely important** that the VMware plugin is upgraded to 1.0.0 or +above. This release resolved critical security vulnerabilities. To learn more, +please [read our release announcement](https://www.hashicorp.com/blog/introducing-the-vagrant-vmware-desktop-plugin). + +After upgrading, please verify that the following paths are empty. The upgrade +process should remove these for you, but for security reasons it is important +to double check. If you're a new user or installing the VMware provider on a +new machine, you may skip this step. + +Specifically, the path `~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation}` +should no longer exist. The gem `vagrant-vmware-desktop` will exist since this +is the name of the new plugin. If the old directories exist, remove them. An +example for a Unix-like shell is shown below: + +```shell +# Check if they exist and verify that they're the correct paths as shown below. +$ ls ~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation} +... + +# Remove them +$ rm -rf ~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation} +``` + ## Frequently Asked Questions **Q: I purchased a Vagrant VMware plugin license, but I did not receive an email?**
From 503dd89017d049bda1aefea31273d9d215b041ba Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Tue, 27 Mar 2018 15:00:19 -0700 Subject: [PATCH 2/2] Update installation.html.md --- website/source/docs/vmware/installation.html.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/source/docs/vmware/installation.html.md b/website/source/docs/vmware/installation.html.md index 16e0ffab6..fa6f263b6 100644 --- a/website/source/docs/vmware/installation.html.md +++ b/website/source/docs/vmware/installation.html.md @@ -70,10 +70,11 @@ please [read our release announcement](https://www.hashicorp.com/blog/introducin After upgrading, please verify that the following paths are empty. The upgrade process should remove these for you, but for security reasons it is important to double check. If you're a new user or installing the VMware provider on a -new machine, you may skip this step. +new machine, you may skip this step. If you're a Windows user, you may skip this +step as well. -Specifically, the path `~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation}` -should no longer exist. The gem `vagrant-vmware-desktop` will exist since this +The path `~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation}` +should no longer exist. The gem `vagrant-vmware-desktop` may exist since this is the name of the new plugin. If the old directories exist, remove them. An example for a Unix-like shell is shown below: