Perhaps the http 4.1.1 gem (last updated 3/12/2019) should be used instead of httpclient 2.8.3 (last updated 12/9/2016)?
On Wednesday, March 27, 2019 at 4:47:52 PM UTC-4, Madison Smith wrote: > > I'm looking in to Drupal VM which uses Vagrant to deploy a Drupal VM. > > I am behind a corporate proxy/firewall and I've already appended our > corporate authority to the C:\HashiCorp\Vagrant\embedded\cacert.pem file. > > After doing so, I'm getting another error: > > > Message: OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 > state=SSLv3 read finished A: unexpected message> > > I've attached a file with full debug output but I believe my issue is > caused by using SSLv3 (looking at the state field) which uses broken > ciphers and is disabled on our network and in Windows. How can I ensure TLS > 1.1 or greater is being used here? > > Is there a configuration setting I can specify in the VagrantFile or is > there a gem I need to update? > > Thank you! > > > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/b9ae56d4-9f07-4cfd-851b-e2be6fe79cd6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
