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

[Richard Achmatowicz (JIRA)]

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

Richard Achmatowicz commented on JGRP-2152:
-------------------------------------------

I can't find any references to ENCRYPT in the testsuite, so probably 
not. Copying Michal to see if there is any testing from QA which makes 
use of JGroups authentication or encryption.

You have a configuration (asym_encrypt) which uses the same 
configuration, so I assume that that sym_algorithm format used in the 
test is supported.

It could be a problem with the forward slashes. I'll do a test myself to 
see what is going on. Report back later today.

Richard




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