Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1294
I am currently making some commits to this PR (on a local branch which I
will post later) to resolve some of the issues recently encountered:
* Improper access scope of property fields
* Unit tests incorrectly modified to reference raw `name` instead of
`displayName` in validation error messages
* `Public Keyring` property pointed at `Private Keyring`
* Incorrectly reverted default KDF from `Bcrypt` to `Legacy KDF`
(deprecated)
As this touches sensitive code within the application (not only does it add
a new processor which users will trust to encrypt sensitive attributes, but it
also rewrites `EncryptContent` which is already widely-used in production
systems), we need to be very careful that regression tests are passing, the
cryptographic code is correct and safe, and we follow the principle of least
surprise for users.
---
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.
---
