iTextG still using Bouncy Castle ("BC") instead of Spongy Castle ("SC") for certain operations

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
Report Content as Inappropriate

iTextG still using Bouncy Castle ("BC") instead of Spongy Castle ("SC") for certain operations

From the iTextG 5.5.7 source code around com.itextpdf.text.pdf.security.CertificateVerification:197:

public static boolean verifyOcspCertificates(BasicOCSPResp ocsp, KeyStore keystore, String provider) {
   if (provider == null)
       provider = "BC";
   try {
       for (Enumeration<String> aliases = keystore.aliases(); aliases.hasMoreElements();) {

It is using the "BC" string where it should use "SC", quoting from https://rtyley.github.io/spongycastle/:

the Java Security API Provider name is now SC rather than BC

Note that the previous one is only one example where the "BC" provider name is still used, other ocurrences can be found by searching in the iTextG source code.


Jaime Hablutzel -  RPC 994690880

Give your users amazing mobile app experiences with Intel XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2-D/3-D games for multiple OSs.
Then get your creation into app stores sooner, with many ways to monetize.
iText-questions mailing list
[hidden email]

iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php