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

List:       xmlrpc-user
Subject:    [jira] [Created] (WSS-572) EncryptedKeyProcessor does not respect the CryptoProvider when initializi
From:       Christian_Mäder_(JIRA) <jira () apache ! org>
Date:       2016-02-29 10:23:18
Message-ID: JIRA.12945407.1456741356000.171328.1456741398077 () Atlassian ! JIRA
[Download RAW message or body]

Christian M=C3=A4der created WSS-572:
-----------------------------------

             Summary: EncryptedKeyProcessor does not respect the CryptoProv=
ider 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=C3=A4der
            Assignee: Colm O hEigeartaigh
         Attachments: feature_cipher_from_provider.diff

During the decryption I had the problem, that the Cipher was instantiated f=
rom BouncyCastle, but my (asymmetric) Key was from a different provider. Th=
at'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 instan=
tiated from the same provider as the Key. It also does a little bit of refa=
ctoring 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] 

Configure | About | News | Add a list | Sponsored by KoreLogic