new repository

1 files changed, 10 insertions, 0 deletions

diff --git a/devdocs/vagrant/share%2Fsecurity.html b/devdocs/vagrant/share%2Fsecurity.html
new file mode 100644
index 00000000..9b90f755
--- /dev/null
+++ b/devdocs/vagrant/share%2Fsecurity.html
@@ -0,0 +1,10 @@
+<h1 id="security">  Security </h1> <p>Sharing your Vagrant environment understandably raises a number of security concerns.</p> <p>The primary security mechanism for Vagrant Share is security through obscurity along with an encryption key for SSH. Additionally, there are several configuration options made available to help control access and manage security:</p> <ul> <li>
+<a href="#disable-http"><code>--disable-http</code></a> will not create a publicly accessible HTTP URL. When this is set, the only way to access the share is with <code>vagrant connect</code>. </li> </ul> <p>In addition to these options, there are other features we've built to help:</p> <ul> <li>
+<p>Vagrant share uses end-to-end TLS for non-HTTP 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.</p> </li> <li>
+<p>SSH keys are encrypted by default, using a password that is not transmitted to our servers or across the network at all.</p> </li> <li>
+<p>SSH is not shared by default, it must explicitly be shared with the <code>--ssh</code> flag.</p> </li> </ul> <p>Most importantly, you must understand that by running <code>vagrant share</code>, you are making your Vagrant environment accessible by anyone who knows the share name. When share is not running, it is not accessible.</p><div class="_attribution">
+  <p class="_attribution-p">
+    &copy; 2010&ndash;2018 Mitchell Hashimoto<br>Licensed under the MPL 2.0 License.<br>
+    <a href="https://www.vagrantup.com/docs/share/security.html" class="_attribution-link">https://www.vagrantup.com/docs/share/security.html</a>
+  </p>
+</div>