[jboss-jira] [JBoss JIRA] (JGRP-2152) ASYM_ENCRYPT failure on Wildfly 10.1.0

[Bela Ban (JIRA)]

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

Bela Ban edited comment on JGRP-2152 at 1/13/17 3:10 AM:
---------------------------------------------------------

ASYM_ENCRYPT requires AUTH, can you retry with AUTH? See \[1\] in my original comment. Which version of JGroups did you use here? I see that Wildfly master uses 3.6.11 (?), which does NOT have the fix \[1\].

\[1\] https://issues.jboss.org/browse/JGRP-2131


was (Author: belaban):
ASYM_ENCRYPT requires AUTH, can you retry with AUTH? See \[1\] in my original comment.

> ASYM_ENCRYPT failure on Wildfly 10.1.0
> --------------------------------------
>
>                 Key: JGRP-2152
>                 URL: https://issues.jboss.org/browse/JGRP-2152
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.6.10
>            Reporter: Matt Wringe
>            Assignee: Bela Ban
>             Fix For: 4.0, 3.6.13
>
>         Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log, org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output.txt, standalone.xml
>
>
> Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
> I am using the parameters for ASYM_ENCRYPT specified in http://www.jgroups.org/manual/index.html#Security
> Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my setup. Its only ASYM_ENCRYPT which is currently failing.
> Note: running this on EAP fails in a similar manner.
> Eg:
> <protocol type="ASYM_ENCRYPT">
>   <property name="encrypt_entire_message">true</property>
>   <property name="sym_keylength">128</property>
>   <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
>   <property name="asym_keylength">512</property>
>   <property name="asym_algorithm">RSA</property>
> </protocol>
> If I run a single instance, then I don't see any problems appear in the logs. Its when I start a second instance that I start to see errors about unrecognised ciphers and timeouts.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)