You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Namrata Jaiswal (JIRA)" <ji...@apache.org> on 2016/02/02 10:44:39 UTC
[jira] [Created] (WSS-566) AES_GCM_128 does not work for
attachments
Namrata Jaiswal created WSS-566:
-----------------------------------
Summary: AES_GCM_128 does not work for attachments
Key: WSS-566
URL: https://issues.apache.org/jira/browse/WSS-566
Project: WSS4J
Issue Type: Bug
Components: WSS4J Core
Affects Versions: 2.0.1
Reporter: Namrata Jaiswal
Assignee: Colm O hEigeartaigh
Priority: Critical
When trying use stax APIs to encrypt and decrypt attachments using AES_GCM_128, it breaks with error saying
Caused by: java.lang.IllegalStateException: Cipher not initialized
at javax.crypto.Cipher.d(Unknown Source)
at javax.crypto.Cipher.doFinal(Unknown Source)
at javax.crypto.CipherInputStream.close(Unknown Source)
Please note that same code works for AES_128 with attachments.
Also, I looked into the code stax code, found that org.apache.xml.security.stax.impl.processor.input.AbstractDecryptInputProcessor.processEvent(InputProcessorChain, boolean) has
final int ivLength = JCEAlgorithmMapper.getIVLengthFromURI(algorithmURI) / 8;
Not sure if ivLength used for GCM could be the problem?
--
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