Permalink
Browse files

Yay SSL #464

  • Loading branch information...
1 parent c82d5c7 commit a46eeefd211269ab5cbdd7569292699bf1eab47d @janl janl committed Jun 21, 2012
Showing with 2 additions and 2 deletions.
  1. +1 −1 draft/security.html
  2. +1 −1 editions/1/en/security.html
View
@@ -124,7 +124,7 @@ <h3 id="authentication">Basic Authentication</h3>
<p>If you are security conscious, the missing <code>s</code> in <code>http://</code> will make you nervous. We’re sending our password to CouchDB in plain text. This is a bad thing, right? Yes, but consider our scenario: CouchDB listens on <code>127.0.0.1</code> on a development box that we’re the sole user of. Who could possibly sniff our password?
-<p>If you are in a production environment, however, you need to reconsider. Will your CouchDB instance communicate over a public network? Even a LAN shared with other colocation customers is public. There are multiple ways to secure communication between you or your application and CouchDB that exceed the scope of this book. We suggest you read up on VPNs and setting up CouchDB behind an HTTP proxy (like Apache httpd’s mod_proxy, nginx, or varnish) that will handle SSL for you. CouchDB does not support exposing its API via SSL at the moment. It can, however, replicate with other CouchDB instances that are behind an SSL proxy.
+<p>If you are in a production environment, however, you need to reconsider. Will your CouchDB instance communicate over a public network? Even a LAN shared with other colocation customers is public. There are multiple ways to secure communication between you or your application and CouchDB that exceed the scope of this book. <strike>We suggest you read up on VPNs and setting up CouchDB behind an HTTP proxy (like Apache httpd’s mod_proxy, nginx, or varnish) that will handle SSL for you. CouchDB does not support exposing its API via SSL at the moment. It can, however, replicate with other CouchDB instances that are behind an SSL proxy</strike> CouchDB as of version 1.1.0 comes with <a href="http://wiki.apache.org/couchdb/How_to_enable_SSL">SSL built in</a>.
<h4 id="validation">Update Validations Again</h4>
@@ -124,7 +124,7 @@ <h3 id="authentication">Basic Authentication</h3>
<p>If you are security conscious, the missing <code>s</code> in <code>http://</code> will make you nervous. We’re sending our password to CouchDB in plain text. This is a bad thing, right? Yes, but consider our scenario: CouchDB listens on <code>127.0.0.1</code> on a development box that we’re the sole user of. Who could possibly sniff our password?
-<p>If you are in a production environment, however, you need to reconsider. Will your CouchDB instance communicate over a public network? Even a LAN shared with other colocation customers is public. There are multiple ways to secure communication between you or your application and CouchDB that exceed the scope of this book. We suggest you read up on VPNs and setting up CouchDB behind an HTTP proxy (like Apache httpd’s mod_proxy, nginx, or varnish) that will handle SSL for you. CouchDB does not support exposing its API via SSL at the moment. It can, however, replicate with other CouchDB instances that are behind an SSL proxy.
+<p>If you are in a production environment, however, you need to reconsider. Will your CouchDB instance communicate over a public network? Even a LAN shared with other colocation customers is public. There are multiple ways to secure communication between you or your application and CouchDB that exceed the scope of this book. <strike>We suggest you read up on VPNs and setting up CouchDB behind an HTTP proxy (like Apache httpd’s mod_proxy, nginx, or varnish) that will handle SSL for you. CouchDB does not support exposing its API via SSL at the moment. It can, however, replicate with other CouchDB instances that are behind an SSL proxy</strike> CouchDB as of version 1.1.0 comes with <a href="http://wiki.apache.org/couchdb/How_to_enable_SSL">SSL built in</a>.
<h4 id="validation">Update Validations Again</h4>

0 comments on commit a46eeef

Please sign in to comment.