UAC issues on Windows

[evertiro]

On Windows, hostsupdater fails unless vagrant is run as an administrator. Unfortunately, this is really not the smart way to run vagrant. I know you can elevate privileges through WIN32OLE, but I'm not familiar enough with ruby to actually patch it myself. Thoughts?

[tkdb]

Open %SystemRoot%\system32\drivers\etc in Windows Explorer, locate the hosts file, right-click it and set the usage rights to the current user (the one you run vagrant under) to allow file modification.

The plugin has no problems to work then, you don't need to run vagrant as administrator.

[tkdb]

If you want to do that in a semi-automatic fashion, I've created some cmd scripts that are capable of doing so.

[itsananderson]

So, I probably should have checked the project issues before working on this, but I've also written a solution.

https://github.com/itsananderson/vagrant-hostsupdater

The main difference between my workaround and @tkdb's is mine asks for UAC escalation "on-demand" each time it modifies the hosts file, so write permissions on the hosts file aren't changed at all.

If we want to use all or part of my solution, I can clean it up for a PR.

[tkdb]

@itsananderson Thanks for the feedback. From quick review I'd say your code is worth for PR (I'm not speaking for the vagrant-hostsupdater project here just my personal opinion as a user and developer), if you can make it into a PR referencing this issue would be great, then I can give it a test-drive here on my box.

Edit: Later I spotted Powershell as dependency which is not necessarily part of windows - available checks (as well as fail checks) are missing.

[jeremiahsmall]

@itsananderson +1 for removing powershell dependency and PR'ing this.

[itsananderson]

I got busy with other things and lost track of this. I think removing the PS dependency should be doable, I just need to find the time to rewrite it. I'll see if I can set aside some time over the next weekend or two. Feel free to ping me if I forget again :)

EDIT: Looks like there was already a commit back in November that seems to solve this issue?

[bretmogilefsky]

@itsananderson Can you give a pointer to that commit please? Not seeing it in the commit log for this repository.

[itsananderson]

Oh, I was wrong. I saw this: willenglishiv@d5b031c and incorrectly thought it was in the original repo.

I'll see if I can use that commit as a reference for doing UAC elevation in CMD, so we can get this fix into a PR.

[bretmogilefsky]

@itsananderson That'd be great!

[polarathene]

Just ran into this issue, since the last commit to the plugin was 2013 has development on this repo likely stopped for good? Which repo were you going to send the PR to?

[jeremiahsmall]

Hmm, @Cogitatio has been totally silent on GitHub for the previous year. Maybe he wouldn't mind if someone took over maintenance?