Closed ericduran closed 9 years ago
This happens to me as well. +1
I don't mind if the script did a privilege escalation in the beginning and asked for my sudo password immediately. That would be fine.
@ericduran @msound OK, how about we make an option to disable Hostupdater. Most people will use it (because it's easy, and requires no manual steps), but advanced users can add hostupdater = disabled
to their config.yml
, and will be responsible for adding hosts file entries manually. Would that make it less annoying?
@scottrigby I was thinking I will edit my sudoers
file and give myself permission to run hostsupdater
with the option NOPASSWD
. That way it wont prompt me for password. On the other hand, I am not sure how insecure this idea is.
There is an issue for that https://github.com/cogitatio/vagrant-hostsupdater/issues/54. I was thinking that we can circumvent this though in our own Vagrantfile
, since we call it ourselves. We could just opt to not do that based on a custom config
Just saw #136 merged. Closing the issue
Whoa @ericduran @msound check out this (maybe better) solution: https://github.com/cogitatio/vagrant-hostsupdater/issues/54#issuecomment-62791060 Update: ha don't do this. Our way is better for more than one reason.
Yea, I know about sudoers but I like the optional hostupdater because I genuinely don't want my host files changing.
@ericduran ah that makes sense. Also like i said on slack i have one other reason not to do this – the NOPASSWD option seems to be locking the primary user out of sudo. Fun times! (updating orig comment to strongly recommend against on a Mac).
@scottrigby I also knew about sudoers, but wasn't sure if I wanted to do that. I am leaning towards running my own BIND9 DNS server and then spoofing entries from a zone file(s).
I usually type vagrant up, and then go do something and I come back and the prompt is just waiting for sudo pass :-/