New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ssh.insert_key in centos-7.1 and centos-7.2 boxes vagrant provider= vmware_fusion #641

Closed
ghost opened this Issue Aug 1, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@ghost

ghost commented Aug 1, 2016

Hi bento team,

have an issue tested on centos-7.1 and centos-7.2 boxes.
The insecure_public_key will replaced by vagrant, but the file-permissions of /home/vagrant/.ssh/authorized_keys then set to 664. A login is only possible with file-permissions 600.
Maybe a umask problem.
I use right now the workaround, to start the machine with 'config.ssh.insert_key=false' and replace the authorized_keys by hand.

Kind Regards
SierraX369

@rickard-von-essen

This comment has been minimized.

Show comment
Hide comment
@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Aug 1, 2016

Sorry forgot my setup:
vmware-fusion = 8.1.1 (3771013)
vagrant = 8.1.5
plugin:
vagrant-vmware-fusion = 4.0.10

ghost commented Aug 1, 2016

Sorry forgot my setup:
vmware-fusion = 8.1.1 (3771013)
vagrant = 8.1.5
plugin:
vagrant-vmware-fusion = 4.0.10

@legal90

This comment has been minimized.

Show comment
Hide comment
@legal90

legal90 Aug 1, 2016

Contributor

As @rickard-von-essen has mentioned above, that's the known issue of Vagrant 1.8.5 (hashicorp/vagrant#7610), which was already fixed in vagrant's master branch by hashicorp/vagrant#7611.

This issue is reproducible for all RHEL-based Linux guests and all providers with Vagrant 1.8.5.
We are looking forward to Vagrant 1.8.6 with the fix being released soon. Currently you can work it around by downgrading to Vagrant v1.8.4: https://releases.hashicorp.com/vagrant/1.8.4/

I'm gonna close this, since there is nothing to do on the Bento's side.

Contributor

legal90 commented Aug 1, 2016

As @rickard-von-essen has mentioned above, that's the known issue of Vagrant 1.8.5 (hashicorp/vagrant#7610), which was already fixed in vagrant's master branch by hashicorp/vagrant#7611.

This issue is reproducible for all RHEL-based Linux guests and all providers with Vagrant 1.8.5.
We are looking forward to Vagrant 1.8.6 with the fix being released soon. Currently you can work it around by downgrading to Vagrant v1.8.4: https://releases.hashicorp.com/vagrant/1.8.4/

I'm gonna close this, since there is nothing to do on the Bento's side.

@legal90 legal90 closed this Aug 1, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment