From cd3f43902ae9040ad668b3a2cda6880238ba00b9 Mon Sep 17 00:00:00 2001 From: Mitchell Hashimoto Date: Wed, 26 Feb 2014 10:13:44 -0800 Subject: [PATCH] Update 2014-02-24-feature-preview-vagrant-1-5-share.html.markdown --- ...14-02-24-feature-preview-vagrant-1-5-share.html.markdown | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/www/source/blog/2014-02-24-feature-preview-vagrant-1-5-share.html.markdown b/website/www/source/blog/2014-02-24-feature-preview-vagrant-1-5-share.html.markdown index 64cbbdbff..7882df022 100644 --- a/website/www/source/blog/2014-02-24-feature-preview-vagrant-1-5-share.html.markdown +++ b/website/www/source/blog/2014-02-24-feature-preview-vagrant-1-5-share.html.markdown @@ -174,6 +174,10 @@ help control access and manage security: In addition to these options, there are other features we've built to help: + * Vagrant share uses end-to-end TLS connections. So even unencrypted TCP streams + are encrypted through the various proxies and only unencrypted during the final + local communication between the local proxy and the Vagrant environment. + * SSH keys are encrypted by default, using a password that is not transmitted to our servers or across the network at all. @@ -237,4 +241,4 @@ account in the yet to be announced web service. At that time, we'll publish further details about share, connect and the account required to use them. -Next week, we'll cover another feature of Vagrant 1.5 — stay tuned. +Next week, we'll cover another feature of Vagrant 1.5 -- stay tuned.