You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2025/02/24 20:43:00 UTC

[jira] [Updated] (NIFI-14293) Remove Bouncy Castle Provider from Cipher Processors

     [ https://issues.apache.org/jira/browse/NIFI-14293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann updated NIFI-14293:
------------------------------------
    Status: Patch Available  (was: Open)

> Remove Bouncy Castle Provider from Cipher Processors
> ----------------------------------------------------
>
>                 Key: NIFI-14293
>                 URL: https://issues.apache.org/jira/browse/NIFI-14293
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Cipher Processors bundle includes EncryptContentAge and DecryptContentAge as well as VerifyContentMAC. The age-encryption.org Processors required the Bouncy Castle Provider to work on Java 8 when they were introduced for NiFi 1. With Java 11 providing support for X25519 and ChaCha20-Poly1305, and with NiFi 2 requiring Java 21, Bouncy Castle is no longer needed as a security provider. The VerifyContentMAC Processor uses the Hex utility class from Bouncy Castle, which can be replaced with the Java HexFormat class to remove all references to the Bouncy Castle library from the module.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)