incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sander Dijkhuis <m...@sanderdijkhuis.nl>
Subject Re: Apache couchDB CA signed certificate issues
Date Wed, 12 Jun 2013 14:28:23 GMT
What kind of problems should I expect with native SSL? I’ve just set up CouchDB with a self-signed
certificate, and that seems to work fine for my purposes.

If it’s advised against, maybe this manual page should mention that:
http://docs.couchdb.org/en/latest/configuring.html#native-ssl-support

On Jun 12, 2013, at 16:14 , Jason Smith <jhs@apache.org> wrote:

> That was the single most problematic CouchDB commit I have ever had to deal
> with. (Bob's work was fine; but it forced an introduction I regretted
> having.)
> 
> 
> On Wed, Jun 12, 2013 at 9:03 PM, Robert Newson <rnewson@apache.org> wrote:
> 
>> and by "never", I strictly mean "for a very brief period where I added
>> native SSL support to CouchDB in 2010".
>> 
>> B.
>> 
>> 
>> On 12 June 2013 15:01, Robert Newson <rnewson@apache.org> wrote:
>>> I'd recommend haproxy 1.5 anyway, I've never been a big fan of
>>> erlang's built-in SSL support (and it has a fairly yucky history of
>>> bugs).
>>> 
>>> B.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message