[
https://issues.apache.org/jira/browse/HDDS-10708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szabolcs Gál resolved HDDS-10708.
---------------------------------
Resolution: Fixed
This pull request fixed this issue:
[https://github.com/apache/ozone/pull/6548]
In the end getting the default algorithm was completely fine so instead of JKS
we are using that and it can be later configured in the security properties.
> Create configuration option for key/truststore factory default algorithm
> ------------------------------------------------------------------------
>
> Key: HDDS-10708
> URL: https://issues.apache.org/jira/browse/HDDS-10708
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Szabolcs Gál
> Assignee: Szabolcs Gál
> Priority: Major
> Labels: pull-request-available
>
> Key and trustmanager factories are instantiated using .getDefaultAlgorithm()
> method calls which can be colliding with cryptography complience. Create a
> configuration option that contains this as a default value and use the
> CRYPTO_COMPLIANCE tag.
> After more thorough consideration the keystore and truststore default
> algorithm could stay and configuring them as a security property is
> completely fine.
> Here is the pull request that switched the JKS implementations to getting the
> default algorithms. [https://github.com/apache/ozone/pull/6548]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
