From ee3dfc3e8987c80c4b3f46f0aeee68a5aa96c2c5 Mon Sep 17 00:00:00 2001 From: Paul Hammant Date: Sat, 10 Sep 2016 11:55:01 -0400 Subject: [PATCH] link to docker image - klaemo/couchdb-ssl --- draft/security.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft/security.html b/draft/security.html index b617b8e..5ae5efb 100644 --- a/draft/security.html +++ b/draft/security.html @@ -124,7 +124,7 @@

Basic Authentication

If you are security conscious, the missing s in http:// 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 127.0.0.1 on a development box that we’re the sole user of. Who could possibly sniff our password? -

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 CouchDB as of version 1.1.0 comes with SSL built in. +

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 CouchDB as of version 1.1.0 comes with SSL built in. You may also want to try a Docker image with SSL enabled out of the box.

Update Validations Again