ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Namrata Jaiswal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WSS-566) AES_128_GCM does not work for attachments
Date Wed, 02 Mar 2016 12:49:18 GMT

     [ 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 can we expect release of WSS4J 2.0.7?

Thanks,
Namrata



From:	"Colm O hEigeartaigh (JIRA)" <jira@apache.org>
To:	Namrata Jaiswal/India/IBM@IBMIN
Date:	02/03/2016 03:33 PM
Subject:	[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15130153#comment-15130153
 ]

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

Maybe in about 5/6 weeks or so.

Colm.

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
>
>
> 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


Mime
View raw message