From f13220cd748d67430f4236eefff9dfa69ef68237 Mon Sep 17 00:00:00 2001 From: Casey Lang Date: Fri, 31 Jul 2015 14:10:57 -0400 Subject: [PATCH] Clarify config.ssh.insert_key docs Modified the description of `config.ssh.insert_key` a bit to improve readability. --- website/docs/source/v2/vagrantfile/ssh_settings.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/source/v2/vagrantfile/ssh_settings.html.md b/website/docs/source/v2/vagrantfile/ssh_settings.html.md index b07835b75..cadeca060 100644 --- a/website/docs/source/v2/vagrantfile/ssh_settings.html.md +++ b/website/docs/source/v2/vagrantfile/ssh_settings.html.md @@ -68,12 +68,12 @@ is enabled. Defaults to false.
`config.ssh.insert_key` - If `true`, Vagrant will automatically insert -an keypair to use for SSH, replacing the default Vagrant's insecure key +a keypair to use for SSH, replacing Vagrant's default insecure key inside the machine if detected. By default, this is true. This only has an effect if you don't already use private keys for authentication or if you are relying on the default insecure key. -If you don't have to take care about security in your project and want to +If you don't have to care about security in your project and want to keep using the default insecure key, set this to `false`.