[
https://issues.apache.org/jira/browse/OAK-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112404#comment-15112404
]
Alex Parvulescu commented on OAK-3761:
--------------------------------------
{quote}
Does Oak need automatic encryption or has other use case for encryption ?
{quote}
I don't think it's this simple. The way I see it (nothing against crypto
support itself) is: does Oak need to _implement itself_ the crypto support, or
can it simply 'enable' on demand it via a plugin mechanism and a loose
dependency to an external library that provides this support.
Could we use it? Sure! Do we need to roll our own crypto? Not convinced.
> Oak crypto API and implementation
> ---------------------------------
>
> Key: OAK-3761
> URL: https://issues.apache.org/jira/browse/OAK-3761
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: security
> Affects Versions: 1.3.12
> Reporter: Timothee Maret
> Assignee: angela
> Attachments: OAK-3761.patch, OAK-3761.patch
>
>
> As discussed in [0], this issue tracks adding a simple API and implementation
> for encryption/decryption in Oak.
> [0]
> http://oak.markmail.org/search/?q=crypto#query:crypto+page:1+mid:iwsfd66lku2dzs2n+state:results
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
