ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (WSS-572) EncryptedKeyProcessor does not respect the CryptoProvider when initializing a new Cipher
Date Tue, 01 Mar 2016 11:07:18 GMT

     [ https://issues.apache.org/jira/browse/WSS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Colm O hEigeartaigh resolved WSS-572.
-------------------------------------
    Resolution: Fixed

> 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, feature_cipher_from_provider_2.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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


Mime
View raw message