From f9295c44f05b662132164bc611ce084ab1903aed Mon Sep 17 00:00:00 2001 From: emdee Date: Thu, 22 Sep 2022 04:23:53 +0200 Subject: [PATCH] Update 'MultiDeviceInitialization' --- MultiDeviceInitialization.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/MultiDeviceInitialization.md b/MultiDeviceInitialization.md index a666d5d..e466ee3 100644 --- a/MultiDeviceInitialization.md +++ b/MultiDeviceInitialization.md @@ -5,4 +5,6 @@ existing profile. We assume all clients use a common tox profile format, though most complement the Tox profile with an ini file or similar. If you just copy a profile from one device to the next it will not work as -you cannot have 2 profiles with the same keys online at the same time. We could have a simple utility that rekeys a profile and creates a new ToxID, so that we could copy a profile and rekey it. Then the new client running the rekeyed profile could send a DHT announcement updating to the new ToxID. \ No newline at end of file +you cannot have 2 profiles with the same keys online at the same time. We could have a simple utility that rekeys a profile and creates a new ToxID, so that we could copy a profile and rekey it. Then the new client running the rekeyed profile could send a DHT announcement updating to the new ToxID. + +The profile rekey utility could also do other things at the same time, like empty the TCP_RELAYS section of the profile if desired.