-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add information about insecure keypairs for development instances.
- Loading branch information
1 parent
1410854
commit ab26ac4
Showing
3 changed files
with
14 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
# Insecure Keypair | ||
|
||
These keys are the "insecure" public/private keypair we offer to | ||
[base box creators](https://www.vagrantup.com/docs/boxes/base.html) for use in their base boxes so that | ||
vagrant installations can automatically SSH into the boxes. | ||
|
||
If you're working with a team or company or with a custom box and | ||
you want more secure SSH, you should create your own keypair | ||
and configure the private key in the Vagrantfile with | ||
`config.ssh.private_key_path` |