[ 
https://issues.apache.org/jira/browse/HADOOP-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803325#comment-17803325
 ] 

ASF GitHub Bot commented on HADOOP-19024:
-----------------------------------------

pjfanning opened a new pull request, #6410:
URL: https://github.com/apache/hadoop/pull/6410

   ### Description of PR
   
   HADOOP-19024
   
   bouncycastle jdk15 jars are no longer patched. Security fixes only go on the 
jdk18 jars.
   
   ### How was this patch tested?
   
   CI build
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [x] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> change to bouncy castle jdk1.8 jars
> -----------------------------------
>
>                 Key: HADOOP-19024
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19024
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: PJ Fanning
>            Priority: Major
>
> They have stopped patching the JDK 1.5 jars that Hadoop uses (see 
> https://issues.apache.org/jira/browse/HADOOP-18540).
> The new artifacts have similar names - but the names are like bcprov-jdk18on 
> as opposed to bcprov-jdk15on.
> CVE-2023-33201 is an example of a security issue that seems only to be fixed 
> in the JDK 1.8 artifacts (ie no JDK 1.5 jar has the fix).
> https://www.bouncycastle.org/releasenotes.html#r1rv77 latest current release 
> but the CVE was fixed in 1.74.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to