Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion bitrepository-core/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk18on</artifactId>
<version>1.75</version>
<version>1.78</version>
Copy link
Contributor

@ole-v-v ole-v-v Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How far do we want to bump the version? 1.78 gets us away from the vulnerability, so main the purpose is fulfilled. On Maven Central it seems that 1.78.1 is popular, and versions up to 1.83 exist (the last one 2 weeks old). I suggest that we go further than 1.78. I furthermore suggest that we use the same version number for bcprov-jdk18on and bcmail-jdk18on. Both are in group org.bouncycastle, and version numbers seem to correspond.

PS IntelliJ IDEA thinks there’s a different vulnerability in 1.78 that is solved in 1.78.1.

</dependency>
<dependency>
<groupId>org.bouncycastle</groupId>
Expand Down