You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "exceptionfactory (via GitHub)" <gi...@apache.org> on 2026/10/02 16:25:42 UTC
[PR] NIFI-16414 Deprecate BLAKE2b Hash Algorithm for Removal [nifi]
exceptionfactory opened a new pull request, #11752:
URL: https://github.com/apache/nifi/pull/11752
# Summary
[NIFI-16414](https://issues.apache.org/jira/browse/NIFI-16414) Deprecates the BLAKE2b hash algorithm options in `CryptographicHashContent` for removal.
The `CryptographicHashContent` Processor supports a number of algorithms, most of which are implemented using standard Java Cryptography Architecture `MessageDigest`. The BLAKE2b algorithms require the use of Bouncy Castle libraries. NiFi Expression Language supports the `hash()` function, which is limited to `MessageDigest` algorithms, so removing support for BLAKE2b aligns these implementations and reduces project usage of Bouncy Castle in standard libraries.
Subsequent removal of BLAKE2b should be considered in a minor release version.
# Tracking
Please complete the following tracking steps prior to pull request creation.
### Issue Tracking
- [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created
### Pull Request Tracking
- Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000`
- Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000`
- Pull request contains [commits signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) with a registered key indicating `Verified` status
### Pull Request Formatting
- Pull Request based on current revision of the `main` branch
- Pull Request refers to a feature branch with one commit containing changes
# Verification
Please indicate the verification steps performed prior to pull request creation.
### Build
- [ ] Build completed using `./mvnw clean install -P contrib-check`
- [ ] JDK 21
- [ ] JDK 25
### Licensing
- [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html)
- [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files
### Documentation
- [ ] Documentation formatting appears as expected in rendered files
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-16414 Deprecate BLAKE2b Hash Algorithm for Removal [nifi]
Posted by "exceptionfactory (via GitHub)" <gi...@apache.org>.
exceptionfactory commented on code in PR #11752:
URL: https://github.com/apache/nifi/pull/11752#discussion_r4167811771
##########
nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/CryptographicHashContent.java:
##########
@@ -99,6 +104,14 @@ protected List<PropertyDescriptor> getSupportedPropertyDescriptors() {
return PROPERTY_DESCRIPTORS;
}
+ @OnScheduled
+ public void onScheduled(final ProcessContext context) {
+ final HashAlgorithm algorithm = HashAlgorithm.fromName(context.getProperty(HASH_ALGORITHM).getValue());
+ if (algorithm.isBlake2()) {
+ deprecationLogger.warn("{} is deprecated for removal", algorithm.getName());
Review Comment:
That's a good point. Although the deprecation log should be the primary location for tracking, adding a warning in the Component Log seems reasonable here. I will push an update.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-16414 Deprecate BLAKE2b Hash Algorithm for Removal [nifi]
Posted by "pvillard31 (via GitHub)" <gi...@apache.org>.
pvillard31 merged PR #11752:
URL: https://github.com/apache/nifi/pull/11752
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NIFI-16414 Deprecate BLAKE2b Hash Algorithm for Removal [nifi]
Posted by "pvillard31 (via GitHub)" <gi...@apache.org>.
pvillard31 commented on code in PR #11752:
URL: https://github.com/apache/nifi/pull/11752#discussion_r4167767700
##########
nifi-extension-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/CryptographicHashContent.java:
##########
@@ -99,6 +104,14 @@ protected List<PropertyDescriptor> getSupportedPropertyDescriptors() {
return PROPERTY_DESCRIPTORS;
}
+ @OnScheduled
+ public void onScheduled(final ProcessContext context) {
+ final HashAlgorithm algorithm = HashAlgorithm.fromName(context.getProperty(HASH_ALGORITHM).getValue());
+ if (algorithm.isBlake2()) {
+ deprecationLogger.warn("{} is deprecated for removal", algorithm.getName());
Review Comment:
should we also consider adding a component level warn log to show a bulletin?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org