Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bc-fips-2.0.0.jar non-exported packages are used by bcpkix-fips-2.0.7.jar and bcpg-fips-2.0.9.jar #1997

Open
marnix opened this issue Feb 14, 2025 · 0 comments

Comments

@marnix
Copy link

marnix commented Feb 14, 2025

For BC-FJA 2.0.x, we discovered that the PKIX and PGP libraries use/import packages which are not exported by bc-fips-2.0.0.jar, when used as a Java 9+ module (org.bouncycastle.fips.core).

Specifically,

  • bcpkix-fips-2.0.7 does import org.bouncycastle.asn1.isara.IsaraObjectIdentifiers; in multiple places
  • bcpg-fips-2.0.9 (and likely 2.0.10) does import org.bouncycastle.asn1.cryptlib.CryptlibObjectIdentifiers; in multiple places

while neither org.bouncycastle.asn1.isara nor org.bouncycastle.asn1.cryptlib are in bc-fips-2.0.0.jar in META-INF\versions\9\module-info.class.


The obvious workaround that works for us, is to use --add-opens (--add-exports would presumably also work), to allow both org.bouncycastle.fips.core/org.bouncycastle.asn1.isara and org.bouncycastle.fips.core/org.bouncycastle.asn1.cryptlib to be used from our own module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant