On Monday, April 13, 2015 at 8:16:29 AM UTC-7, dragon788 wrote: > > Until you figure out the issue, you can try the workaround in this > comment. > https://github.com/mitchellh/vagrant/issues/5059#issuecomment-68041037 > > Basically config.ssh.insert_key = false into your Vagrantfile should > prevent it from changing the keys, which means it will keep using the old > one. >
I added that line to the file `Vagrantfile` located in `/srv/data/Virtualbox/vagrant/test`, which is the base directory the box I'm attempting to make. Didn't seem to make any difference. > For your issue it sounds like the place that vagrant is trying to store > the new private key file has too loose of permissions, so you need to chmod > the .ssh folder that they live in to 600, which the .pub being 644 > permissions. > > /srv/data/VirtualBox/vagrant/test/.vagrant/machines/default/virtualbox/ >> private_key >> > > monte@machin-shin:/srv/data/VirtualBox/vagrant/test$ >> > Well, that is part of the question. Are we talking my personal `~/.ssh/` folder? Cuz its permissions are 0600, and id_rsa.pub within has permissions of 0644. If we're talking the directory shown above: `/srv/data/VirtualBox/vagrant/test/.vagrant....virtualbox/`, then no it isn't, and neither is the `private_key` file - and *vagrant* created them, and I *can't* change the permissions on them. Thanks, Monte -- 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]. For more options, visit https://groups.google.com/d/optout.
