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

List:       xmlrpc-user
Subject:    [jira] [Updated] (WSS-566) AES_128_GCM does not work for attachments
From:       "Namrata Jaiswal (JIRA)" <jira () apache ! org>
Date:       2016-03-29 9:50:25
Message-ID: JIRA.12935910.1454406220000.74698.1459245025492 () Atlassian ! JIRA
[Download RAW message or body]


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

Namrata Jaiswal updated WSS-566:
--------------------------------
    Attachment: graycol.gif


Hi Colm,

When is WSS4J 2.0.7 releasing?

Thanks,
Namrata



From:	"Colm O hEigeartaigh (JIRA)" <jira@apache.org>
To:	Namrata Jaiswal/India/IBM@IBMIN
Date:	03/22/2016 02:19 PM
Subject:	[jira] [Closed] (WSS-566) AES_128_GCM does not work for
            attachments




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

Colm O hEigeartaigh closed WSS-566.
-----------------------------------

AES_GCM_128, it breaks with error saying
org.apache.xml.security.stax.impl.processor.input.AbstractDecryptInputProcessor.processEvent
 (InputProcessorChain, boolean) has
(algorithmURI) / 8;



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)




> AES_128_GCM 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
> Fix For: 2.0.7, 2.1.5
> 
> Attachments: graycol.gif, graycol.gif, graycol.gif, graycol.gif
> 
> 
> 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


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