From 9e0ff9dc0a59860349fbb89a9209fc5697223fe3 Mon Sep 17 00:00:00 2001 From: emdee Date: Sat, 24 Sep 2022 02:24:48 +0200 Subject: [PATCH] Update 'MultiDeviceInitializationGroups' --- MultiDeviceInitializationGroups.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/MultiDeviceInitializationGroups.md b/MultiDeviceInitializationGroups.md index edcc2d1..3e6f355 100644 --- a/MultiDeviceInitializationGroups.md +++ b/MultiDeviceInitializationGroups.md @@ -6,12 +6,15 @@ But we are left with as special problem with NGC groups. 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. -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?) +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. Besides the group keypair in #L351-2 * bin_pack_bin(bp, chat->chat_public_key, EXT_PUBLIC_KEY_SIZE); // 1 * bin_pack_bin(bp, chat->chat_secret_key, EXT_SECRET_KEY_SIZE); // 2 +The chat->chat_secret_key is all zeros, I assume in everyone but the founder's +profile. + it seems also that self's keypair are saved to the group: * self_public_key #L353 * self_secret_key #L354