[
https://issues.apache.org/jira/browse/NIFI-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871785#comment-15871785
]
ASF GitHub Bot commented on NIFI-2961:
--------------------------------------
Github user HandOfGod94 commented on the issue:
https://github.com/apache/nifi/pull/1294
@alopresto ,
Just an idea crossed my mind. I was thinking of separating out attribute
selection from processor. As we already have a good processor for selecting
attribute(UpdateAttributeProcessor), so user will add suffix to any attribute
which he wants as `.encrypt` and we'll only encrypt those attributes.
It will still contain attribute selection strategy drop down option as
"all/core/selective".
In `selective` mode user has to provide flowfiles having attribute with
`.encrypt` suffix, in order to encrypt it.
It would become faster for us to get the encryption/decryption attributes.
I would like to know your thoughts on this.
Thanks!!
> Create EncryptAttribute processor
> ---------------------------------
>
> Key: NIFI-2961
> URL: https://issues.apache.org/jira/browse/NIFI-2961
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.0.0
> Reporter: Andy LoPresto
> Labels: attributes, encryption, security
>
> Similar to {{EncryptContent}}, the {{EncryptAttribute}} processor would allow
> individual (and multiple) flowfile attributes to be encrypted (either
> in-place or to a new attribute key) with various encryption algorithms (AES,
> RSA, PBE, and PGP).
> Specific compatibility with the {{OpenSSL EVP_BytesToKey}}, {{PBKDF2}},
> {{scrypt}}, and {{bcrypt}} key derivation functions should be included.
> The processor should provide the boolean option to encrypt or decrypt (only
> one operation per instance of the processor). The processor should also allow
> Base64 encoding (aka ASCII armor) for the encrypted attributes to prevent
> byte escaping/data loss.
> If [dangerous processor
> annotations|https://cwiki.apache.org/confluence/display/NIFI/Security+Feature+Roadmap]
> are introduced, this processor should be marked as such and the
> corresponding attribute protection (i.e. provenance before/after, etc.)
> should be applied.
> Originally requested in this [Stack Overflow
> question|https://stackoverflow.com/questions/40294945/nifi-encrypt-json].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
