Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable home folder sharing by default (Parallels Desktop 11+) #257

Merged
merged 1 commit into from
Mar 31, 2016

Conversation

legal90
Copy link
Collaborator

@legal90 legal90 commented Mar 30, 2016

Implements GH-171 for Parallels Desktop 11+

Due to request GH-171 there was a new CLI option added in PD 11:

prlctl set <vm_uuid> --shf-host-defined <off|alldisks|home>

By default all Parallels Desktop VMs has this option set to "home", so that user's home folder (from the Mac host) is accessible for read & write from the guest VMs. In Linux VMs its content could be found at /media/psf/Home

I suggest to set this option to off for all VMs managed by our Vagrant provider, as we do for other host<=>guest integration features (see GH-215). This is needed for security reasons and helps to isolate dev environment from the Mac host.

cc: @Kasen @racktear

@legal90
Copy link
Collaborator Author

legal90 commented Mar 30, 2016

Those users who want to override this behavior, could do it via Vagrantfile:

config.vm.provider "parallels" do |v|
  v.customize ["set", :id, "--shf-host-defined", "home"]
end

@knazarov
Copy link
Contributor

👍

@legal90
Copy link
Collaborator Author

legal90 commented Mar 31, 2016

cc: @rickard-von-essen
Probably, it also makes sense to do the same in Packer builder.

@legal90 legal90 merged commit a180283 into Parallels:master Mar 31, 2016
@legal90 legal90 deleted the disable-home-sharing branch March 31, 2016 08:44
@rickard-von-essen
Copy link

@legal90 Agree, it's probably a better default in Packer too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants