beckermj/vaguerent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update box documentation about keys

Browse Source
This commit is contained in:
Chris Roberts 2023-06-26 15:48:53 -07:00
parent 602d42bbc8
commit 2e95d08309
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/content/docs/boxes/base.mdx
View File

@ -115,15 +115,16 @@ users, passwords, private keys, etc.).
By default, Vagrant expects a "vagrant" user to SSH into the machine as. By default, Vagrant expects a "vagrant" user to SSH into the machine as.
This user should be setup with the This user should be setup with the
[insecure keypair](https://github.com/hashicorp/vagrant/tree/main/keys) [insecure keypairs](https://github.com/hashicorp/vagrant/tree/main/keys)
that Vagrant uses as a default to attempt to SSH. It should belong to a that Vagrant uses as a default to attempt to SSH. It should belong to a
group named "vagrant". Also, even though Vagrant uses key-based group named "vagrant". Also, even though Vagrant uses key-based
authentication by default, it is a general convention to set the authentication by default, it is a general convention to set the
password for the "vagrant" user to "vagrant". This lets people login as password for the "vagrant" user to "vagrant". This lets people login as
that user manually if they need to. that user manually if they need to.
To configure SSH access with the insecure keypair, place the public To configure SSH access with the insecure keypair, place the [public
key into the `~/.ssh/authorized_keys` file for the "vagrant" user. Note keys](https://github.com/hashicorp/vagrant/tree/main/keys/vagrant.pub)
into the `~/.ssh/authorized_keys` file for the "vagrant" user. Note
that OpenSSH is very picky about file permissions. Therefore, make sure that OpenSSH is very picky about file permissions. Therefore, make sure
that `~/.ssh` has `0700` permissions and the authorized keys file has that `~/.ssh` has `0700` permissions and the authorized keys file has
`0600` permissions. `0600` permissions.