[jboss-jira] [JBoss JIRA] (JGRP-2203) ASYM_ENCRYPT: no merge when coord is killed

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-2203:
--------------------------------

A similar issue exists when we have \{A,B,C\} and C leaves gracefully and {{change_key_on_leave}} is true. 

* A creates a new secret key, encrypts view \{A,B\} and broadcasts it. 
* B drops the view because it cannot decrypt it.
* B then asks A for the secret key
* A sends the new secret key to B
* B is now able to decrypt the (retransmitted) view \{A,B\}

Perhaps the common solution for this issue and the issue described above is to have the coordinator send a {{FETCH_SECRET_KEY}} message to all members so they fetch the new secret key via the key exchange protocol.


> ASYM_ENCRYPT: no merge when coord is killed
> -------------------------------------------
>
>                 Key: JGRP-2203
>                 URL: https://issues.jboss.org/browse/JGRP-2203
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 4.0.5
>
>         Attachments: asym-encrypt.xml
>
>
> When we have \{A,B,C\} and A is killed, B and C never end up with the same view. (This works when A leaves gracefully).
> The sample config is attached as asym-encrypt.xml



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