[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlrpc-user
Subject:    [jira] [Commented] (WSS-572) EncryptedKeyProcessor does not respect the CryptoProvider when initiali
From:       "Colm O hEigeartaigh (JIRA)" <jira () apache ! org>
Date:       2016-02-29 12:00:22
Message-ID: JIRA.12945407.1456741356000.171823.1456747222159 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/WSS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171791#comment-15171791 \
] 

Colm O hEigeartaigh commented on WSS-572:
-----------------------------------------

Ok sure.

Colm.

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


[prev in list] [next in list] [prev in thread] [next in thread]