[
https://issues.apache.org/jira/browse/HADOOP-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837922#comment-17837922
]
ASF GitHub Bot commented on HADOOP-19152:
-----------------------------------------
szetszwo commented on PR #6739:
URL: https://github.com/apache/hadoop/pull/6739#issuecomment-2060155541
> the pr cuts out all bouncy castle init. What will break?
@steveloughran , thanks for looking at this! As mentioned in
`core-default.xml`, could we ask admin to set java.security when they set
`hadoop.security.crypto.jce.provider`? The hard code approach currently force
everyone to use a particular version of BouncyCastle provider is incorrect. It
disallows the configurability of java security provider and also disallow
setting a more secure security provider.
```java
+++ b/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
@@ -3623,6 +3623,9 @@ The switch to turn S3A auditing on or off.
<value></value>
<description>
The JCE provider name used in CryptoCodec.
+ If this value is set, the corresponding provider must be added to the
provider list.
+ The provider may be added statically in the java.security file, or
+ added dynamically by calling the java.security.Security.addProvider(..)
method.
</description>
</property>
```
> Do not hard code security providers.
> ------------------------------------
>
> Key: HADOOP-19152
> URL: https://issues.apache.org/jira/browse/HADOOP-19152
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
>
> In order to support different security providers in different clusters, we
> should not hard code a provider in our code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
