You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Andreas Lehmkühler (JIRA)" <ji...@apache.org> on 2017/06/15 16:00:03 UTC
[jira] [Commented] (PDFBOX-3831) v2.0.6 still has hardcoded
reference to BouncyCastleProvider
[ https://issues.apache.org/jira/browse/PDFBOX-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050671#comment-16050671 ]
Andreas Lehmkühler commented on PDFBOX-3831:
--------------------------------------------
You totally right, my bad. Sorry for the confusion. I'm going to fix that
> v2.0.6 still has hardcoded reference to BouncyCastleProvider
> ------------------------------------------------------------
>
> Key: PDFBOX-3831
> URL: https://issues.apache.org/jira/browse/PDFBOX-3831
> Project: PDFBox
> Issue Type: Bug
> Components: Crypto
> Affects Versions: 2.0.6
> Reporter: Naohiro OOHIRA
> Assignee: Andreas Lehmkühler
>
> It seems that PDFBox v2.0.6 still has a hardcoded reference to BouncyCastleProvider, though release note says it was removed.
> * [PDFBOX-2963] - Remove Bouncy Castle Provider Reference
> {code:java}
> public final class SecurityHandlerFactory
> {
> /** Singleton instance */
> public static final SecurityHandlerFactory INSTANCE = new SecurityHandlerFactory();
> static
> {
> Security.addProvider(new BouncyCastleProvider());
> }
> {code}
> Is it as expected that the following modification was only committed to trunk and not committed to 2.0 branch?
> * https://svn.apache.org/viewvc?view=revision&revision=1789414
> I use PDFBox v2.0.5 to parse a pdf file, but don't want it to add dependency to Bouncy Castle because it globally register a Provider instance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org