[
https://issues.apache.org/jira/browse/WSS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Mäder updated WSS-572:
--------------------------------
Attachment: feature_cipher_from_provider.diff
> EncryptedKeyProcessor does not respect the CryptoProvider when initializing a
> new Cipher
> ----------------------------------------------------------------------------------------
>
> Key: WSS-572
> URL: https://issues.apache.org/jira/browse/WSS-572
> Project: WSS4J
> Issue Type: Bug
> Reporter: Christian Mäder
> Assignee: Colm O hEigeartaigh
> Attachments: feature_cipher_from_provider.diff
>
>
> During the decryption I had the problem, that the Cipher was instantiated
> from BouncyCastle, but my (asymmetric) Key was from a different provider.
> That's when things excepted in crazy and hard-to-debug ways.
> The attached patch provides a fix in a way that the Cipher is always
> instantiated from the same provider as the Key. It also does a little bit of
> refactoring towards code, that is easier to grasp (IMO).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
