You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Chung En Lee (Jira)" <ji...@apache.org> on 2025/10/21 20:56:01 UTC
[jira] [Updated] (HDDS-10743) Turn the direct dependency on BouncyCastle to an optional one
[ https://issues.apache.org/jira/browse/HDDS-10743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chung En Lee updated HDDS-10743:
--------------------------------
Target Version/s: 2.2.0
2.2.0 (was: 2.1.0)
<<Bulk update>>
Apache Ozone 2.1.0 release is in progress. I'm updating all unresolved jiras targeting 2.1.0 to retarget 2.2.0.
> Turn the direct dependency on BouncyCastle to an optional one
> -------------------------------------------------------------
>
> Key: HDDS-10743
> URL: https://issues.apache.org/jira/browse/HDDS-10743
> Project: Apache Ozone
> Issue Type: Bug
> Components: Security
> Affects Versions: 1.4.0
> Reporter: István Fajth
> Assignee: István Fajth
> Priority: Major
>
> Our current system is statically linked wih the BouncyCastle JCE Provider and also we directly use some of its implementation details.
> If we would like to allow crypto compliance on the long run, this is a bad practice.
> This task aims to collect all small tasks that can help us to refactor this dependency to be an optional and replaceable one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org