Allow user to define if the box_url is insecure

[igorbonadio]

Currently, it's possible to download a box from an insecure server using the command:

vagrant box add mybox  https://insecureserver.com/mybox.box --insecure

But I think set it in a Vagrantfile is a good feature.

Vagrant.configure("2") do |config|
  config.vm.box = "mybox"
  config.vm.box_url = "https://insecureserver.com/mybox.box"
  config.vm.box_download_insecure = true
end

[fgrehm]

Hey @mitchellh, looks like you fixed this on af66f5f, shall we close this?

[fgrehm]

Hey @mitchellh, looks like you fixed this on af66f5f, shall we close this?

[mitchellh]

Oh I did, yep. Closing! Thanks.

[mitchellh]

Oh I did, yep. Closing! Thanks.

[dragon788]

@mitchellh @sethvargo Since it is a terrible practice to disable SSL verification long term, would it be possible to add instructions on correcting the certificate issue the right way by catching this certificate error exception and giving a helpful suggestion, i.e. adding the certificate to the trust chain of the embedded Ruby and curl or better yet using the alternate CA path that was added to a newer Vagrant version? config.vm.box_download_ca_cert appears to be the new setting.

[dragon788]

@mitchellh @sethvargo Since it is a terrible practice to disable SSL verification long term, would it be possible to add instructions on correcting the certificate issue the right way by catching this certificate error exception and giving a helpful suggestion, i.e. adding the certificate to the trust chain of the embedded Ruby and curl or better yet using the alternate CA path that was added to a newer Vagrant version? config.vm.box_download_ca_cert appears to be the new setting.