My corp proxy thinks vagrant's plugin installer is malware/spyware

[Just Another Vagrant Noob]

When I try "vagrant plugin install vagrant-vbguest", I get error returned from my corporate proxy:

Your browser may have been compromised by a malware/spyware agent identified as "bundler/1.10.5 rubygems/2.0.14 ruby/2.0.0 (i686-pc-mingw32) command/plugin options/path,app_config,bin_path,config,gemfile 3c68a2e26ff65ddf".

Is there a way to configure vagrant's plugin installer to use a different browser agent string?

-Dave

[Alvaro Miranda Aguilera]

Hello,

Just sharing this based on my past experience, not saying this is what you should do, just sharing what I would do.

I think the idea behind the corportate proxy is separate/filter local traffic from internet.

Check with your proxy admin guys if using a CLI tool should work or not.

Based on what the message, you should either get that agent string allowed, or the destination url white listed.

Since impersonating an agent that work, would be potentially seen as "hack" in some paranoid eyes.

Alvaro.

--
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/003be9d3-0f17-40a8-a437-212785550375%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Just Another Vagrant Noob]

Thanks for responding, Alvaro!

I actually do a "bug" filed into IT support to configure the proxy. But I'm coming up with contingency plans in case they don't come through for me.

The plugin installer is actually trying to retrieve http://gems.hashicorp.com/quick/Marshal.4.8/bigdecimal-1.2.6.gemspec.rz when this error comes up. I can wget that URL with no problem. It seems my proxy just doesn't want something that identifies itself as "bundler...." to get it.

On a related note, is there a way to tell the plugin installer, "Hey, don't download bigdecimal-1.2.6.gemspec.rz, just use the one <here>", where 'here' is a local file path?

[John Wallis]

Sorry if this is an irrelevant reply to an old post, but I also recently ran into pretty much the same problem.   Like you I filed a case to configure my corporate firewall, but I only have a moderate level of confidence that will be resolved to my satisfaction.  So I took it upon myself to hack the bundler source with more acceptable User-Agent.  I had asked about this problem last week on askubuntu.com, and so I've self-answered my question with the patch I generated:

http://askubuntu.com/questions/796526/failing-to-install-ruby-gems-required-by-vagrant-plugin-install-vagrant-proxycon/797569#797569

Hope it helps.