From 37bc39f083824003d8ba3452d9aee0fa80698266 Mon Sep 17 00:00:00 2001 From: emdee Date: Fri, 23 Sep 2022 05:27:14 +0200 Subject: [PATCH] Update 'MultiDeviceInitializationGroups' --- MultiDeviceInitializationGroups.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/MultiDeviceInitializationGroups.md b/MultiDeviceInitializationGroups.md index 75fe5f5..f8a20b6 100644 --- a/MultiDeviceInitializationGroups.md +++ b/MultiDeviceInitializationGroups.md @@ -1,12 +1,12 @@ -Previous: [[]] +Previous: [[MultiDeviceInitialization]] In the initialization process we described in [[MultiDeviceInitialization]] we simply copy a profile to a new devices and change the public/private keys as a starting point. But we are left with as special problem with NGC groups. -The code is assumed to have been modified to handle Personas and and first glance, NGC groups become groups of Personas. Each member of the group is the Persona and uses the table lookup to get the active ToxID. But the group structure in the profile has a copy of the founder's shared_state.founder_public_key (group_pack.c#L293) +The code is assumed to have been modified to handle Personas and, at first glance, NGC groups become groups of Personas. Each member of the group is a Persona, and uses the table lookup to get the active ToxID. -So if the profile being copied onto a new device is the profile of the founder, then this key would need to be updated too. (Conversely, does that mean if I copy a profile and update the shared_state.founder_public_key with my own key, do I become the group's founder?) +But the group structure in the profile has a copy of the founder's shared_state.founder_public_key (group_pack.c#L293) So if the profile being copied onto a new device is the profile of the founder, then this key would need to be updated too. (Conversely, does that mean if I copy a profile and update the shared_state.founder_public_key with my own key, do I become the group's founder?) Besides the group keypair in #L351-2 * bin_pack_bin(bp, chat->chat_public_key, EXT_PUBLIC_KEY_SIZE); // 1 @@ -17,5 +17,3 @@ it seems also that self's keypair are saved to the group: * self_secret_key #L354 Are these simply the keypair of the Persona that is the new profile? If so, then these keys have to be updated with the new keypair of the new profile. - -