couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Samuel Newson <>
Subject Re: native encryption for couchdb 4.0?
Date Thu, 12 Mar 2020 17:35:44 GMT

Yes, platform independent, it's not custom C work, just calls into the existing crypto module.

Invisible at the API layer, it's all about the protection of data at rest within FDB.

I don't know enough about _access to answer but I think not. The whole document will need
to be decrypted to access any part of it and this doesn't involve the user.


> On 12 Mar 2020, at 17:17, Joan Touzet <> wrote:
> On 2020-03-12 12:29, Robert Samuel Newson wrote:
>> Hi All,
>> Our team at IBM are working on native encryption of document content for the Cloudant
service and are wondering if there'd be interest (or objection!) to this landing as a CouchDB
> Yes!
>> This is only targeted at the (future) CouchDB 4.0 release which introduces FoundationDB
as the persistence layer and, as stated above, currently only for document bodies.
>> This would be a configuration option (and presumably disabled by default).
>> I'll spare us all the crypto details for now (besides pointing out they've been reviewed
by our in-house cryptographers and use only public algorithms and techniques in a straightforward
> Will the code be platform independent (or at least NIFfed in a way that supports compiling
on Mac, FreeBSD, Windows?)
> Is there any impact on our CouchDB API surface, other than enabling/disabling document
> Is there any intersection with the _access work Jan is working on?
>> Thoughts?
>> B.

View raw message