Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1294
I agree it may be best to restart this effort -- I made a first pass at
resolving some of the issues
[here](https://github.com/alopresto/nifi/tree/NIFI-2961) but there is still
work to do. There's no argument that the original EncryptContent processor
organization can be improved, especially with a new processor which is
performing a lot of the same behavior, as it was originally written many years
ago.
I am currently working on implementing encrypted repositories and the
internal TLS refactor as well as quick fixes for [Allow bootstrap process to
prompt for key](https://issues.apache.org/jira/browse/NIFI-2656) and [First
deployment of NiFi can hang on VMs without sufficient entropy if using
/dev/random/](https://issues.apache.org/jira/browse/NIFI-3113). Do you have an
immediate need for the EncryptAttribute functionality, or can it wait a few
weeks?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
