[
https://issues.apache.org/jira/browse/HDDS-10603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
István Fajth updated HDDS-10603:
--------------------------------
Description:
We have a couple of places, where we either use JCE Provider defaults for
cryptography methods (algos, ciphers hashes etc.), or we explicitly hardwire
one.
The goal of this ticket to serve as an umbrella for sub-tasks that aim to add a
configuration option with the current default value to all of these places one
by one.
In conjunction with this work, additionally if we run into anything that does
not have a general whitelist option yet, we need to add the whitelist option as
part of a sub-task for HDDS-10602.
The scope of this work should cover all the places in the codebase that uses
cryptography and has any code that can be configurable, and does not have a
config option yet. This helps us to ensure we use only compliant cryptography
methods.
Note: places where we use a cryptography function for something that is not
related to authentication, authorization, encryption, decryption, or
identification, we may skip adding new configuration, but we need to mark these
places in the code, and we need to document the purpose, so that compliance
check can decide if it is something that is under the regulation, or it is
irrelevant. (One example might be allowing and MD5 hash to be used for block
checksum, where the MD5 usage is for content integrity verification, as that is
not a security concern at all, with that it is highly likely that an exemption
can be made for those use cases of any crypto function.)
was:
We have a couple of places, where we either use JCE Provider defaults for
cryptography methods (algos, ciphers hashes etc.), or we explicitly hardwire
one.
The goal of this ticket to serve as an umbrella for sub-tasks that aim to add a
configuration option with the current default value to all of these places one
by one.
In conjunction with this work, additionally if we run into anything that does
not have a general whitelist option yet, we need to add the whitelist option as
part of a sub-task for HDDS-10602.
The scope of this work should cover all the places in the codebase that uses
cryptography and has any code that can be configurable, and does not have a
config option yet. This helps us to ensure we use only compliant cryptography
methods.
> Configurable crypto methods all over the project
> ------------------------------------------------
>
> Key: HDDS-10603
> URL: https://issues.apache.org/jira/browse/HDDS-10603
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: István Fajth
> Priority: Major
>
> We have a couple of places, where we either use JCE Provider defaults for
> cryptography methods (algos, ciphers hashes etc.), or we explicitly hardwire
> one.
> The goal of this ticket to serve as an umbrella for sub-tasks that aim to add
> a configuration option with the current default value to all of these places
> one by one.
> In conjunction with this work, additionally if we run into anything that does
> not have a general whitelist option yet, we need to add the whitelist option
> as part of a sub-task for HDDS-10602.
> The scope of this work should cover all the places in the codebase that uses
> cryptography and has any code that can be configurable, and does not have a
> config option yet. This helps us to ensure we use only compliant cryptography
> methods.
> Note: places where we use a cryptography function for something that is not
> related to authentication, authorization, encryption, decryption, or
> identification, we may skip adding new configuration, but we need to mark
> these places in the code, and we need to document the purpose, so that
> compliance check can decide if it is something that is under the regulation,
> or it is irrelevant. (One example might be allowing and MD5 hash to be used
> for block checksum, where the MD5 usage is for content integrity
> verification, as that is not a security concern at all, with that it is
> highly likely that an exemption can be made for those use cases of any crypto
> function.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
