[GitHub] nifi issue #1294: NIFI-2961 Create EncryptAttribute processor

2017-01-07 Thread HandOfGod94
Github user HandOfGod94 commented on the issue:

https://github.com/apache/nifi/pull/1294
  
Hi @alopresto ,
I am done with my modification. It's building successfully as per the 
travis config locally, but fails on their server. The reason is because of 
testcase failures, but when I checked travis config it says 
`-DskipTest=true`, then why is it still executing testcases?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (NIFI-2961) Create EncryptAttribute processor

2017-01-07 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on NIFI-2961:
--

Github user HandOfGod94 commented on the issue:

https://github.com/apache/nifi/pull/1294
  
Hi @alopresto ,
I am done with my modification. It's building successfully as per the 
travis config locally, but fails on their server. The reason is because of 
testcase failures, but when I checked travis config it says 
`-DskipTest=true`, then why is it still executing testcases?


> 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.4#6332)