nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-2961) Create EncryptAttribute processor
Date Tue, 14 Feb 2017 20:39:41 GMT

    [ https://issues.apache.org/jira/browse/NIFI-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866612#comment-15866612
] 

ASF GitHub Bot commented on NIFI-2961:
--------------------------------------

Github user joewitt commented on the issue:

    https://github.com/apache/nifi/pull/1294
  
    It sounds like this PR/discussion has resulted in identifying the need to restart.  I
recommend closing this PR as-is and using the appropriate JIRA(s) to further the discussion.
 Leaving active PRs outstanding can complicate PR review cycles.  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)

Mime
View raw message