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

[ https://issues.jboss.org/browse/JGRP-2203?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-2203 at 7/7/17 4:54 AM: -------------------------------------------------------- The reason is that B as new coord creates a new shared secret and uses it to encrypt and send view \{B,C\}. However, as C doesn't yet have the new shared secret, it won't be able to install the new view. Not getting the view change, C won't know that B is the new key server (it still thinks A is) and therefore C won't ask B for the new shared key. Possible solutions: * Have B encrypt and send the new view with the existing shared key, and change the shared key only after the view installation * Notify everyone of the new key server; this would trigger key fetching from all members. Since such a notification message is sent below the reliable transmission protocols (NAKACK2, UNICAST3), we'd have to send until getting an ack from everyone (kind of like simplistic reliable transmission). was (Author: belaban): The reason is that B as new coord creates a new shared secret and uses it to encrypt and send view \{B,C\}. However, as C doesn't yet have the new shared secret, it won't be able to install the new view. Not getting the view change, C won't know that B is the new key server (it still thinks A is) and therefore C won't ask B for the new shared key. -- This message was sent by Atlassian JIRA (v7.2.3#72005)