[jboss-jira] [JBoss JIRA] Commented: (JGRP-604) ENCRYPT: issues with keystore

Vladimir Blagojevic (JIRA) jira-events at lists.jboss.org
Tue Sep 16 16:10:21 EDT 2008


    [ https://jira.jboss.org/jira/browse/JGRP-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12429908#action_12429908 ] 

Vladimir Blagojevic commented on JGRP-604:
------------------------------------------

The problem seems to be related to encoding of strings in the message payload. If we use RpcDispatcher then MethodCall object is serialized into payload and it contains string for method name. If we change RpcDispatcher.testLargeReturnValue() not to use dispatcher but to simply send messages then the test never fails. 




> ENCRYPT: issues with keystore
> -----------------------------
>
>                 Key: JGRP-604
>                 URL: https://jira.jboss.org/jira/browse/JGRP-604
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Vladimir Blagojevic
>             Fix For: 2.7
>
>         Attachments: tmp2.xml
>
>
> If we use ENCRYPT with a keystore and fragmentation, then ENCRYPT throws the following exception:
> 09:35:45,920 [WARN] [Incoming,demo,192.168.2.3:49952] ENCRYPT.up(): exception occurred decrypting message
> javax.crypto.BadPaddingException: Given final block not properly padded
> 	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
> 	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
> 	at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275)
> 	at javax.crypto.Cipher.doFinal(DashoA12275)
> 	at org.jgroups.protocols.ENCRYPT._decrypt(ENCRYPT.java:837)
> 	at org.jgroups.protocols.ENCRYPT.decryptMessage(ENCRYPT.java:830)
> 	at org.jgroups.protocols.ENCRYPT.handleUpMessage(ENCRYPT.java:673)
> 	at org.jgroups.protocols.ENCRYPT.up(ENCRYPT.java:533)
> 	at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:573)
> 	at org.jgroups.protocols.UNICAST.up(UNICAST.java:247)
> 	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:704)
> 	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
> 	at org.jgroups.protocols.FD.up(FD.java:322)
> 	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:309)
> 	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
> 	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
> 	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
> 	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1456)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:613)
> To reproduce:
> - Create a configuration with the following entries present:
>   <ENCRYPT key_store_name="defaultStore.keystore"  store_password="changeit" alias="myKey"/>	
>   <FRAG2 frag_size="60000"/>
> - Run RpcDispatcherTest.testLargeReturnValue (the stack has to include ENCRYPT and FRAG2).
> Note that this error does not occur with
> <ENCRYPT encrypt_entire_message="false" sym_init="128" sym_algorithm="AES/ECB/PKCS5Padding" asym_init="512" asym_algorithm="RSA"/>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list