Task #1963

implement private key conflict handling

Added by hans about 4 years ago. Updated about 4 years ago.

Status:NewStart date:09/27/2013
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:0.3
Component:

Description

for more of the information that keysync finds, it can include multiple bits of information. For example, if it finds multiple verified fingerprints for a given account, it can just include them all and the apps will all use them. But there can only be one single secret key assigned to a given account.

If someone is syncing multiple apps that have been setup with the same account, it is very likely that each app will have already generated a secret key. That means when syncing, the user will have to choose which secret key to use.


Related issues

Related to KeySync - Task #1868: how best to handle multiple public remote keys, fingerpri... New 09/12/2013
Related to KeySync - Bug #2049: "Did not match" output New 10/10/2013

History

#2 Updated by hans about 4 years ago

  • Target version changed from 0.2 to 0.3

#3 Updated by hans about 4 years ago

  • Priority changed from Normal to High

#4 Updated by hans about 4 years ago

One idea is to choose on secret key and use that for all accounts. That makes it more likely there will be verified sessions, but then links all the accounts the user has together. That might be problematic at times. For more on this topic:

http://lists.cypherpunks.ca/pipermail/otr-dev/2013-November/001973.html

Really, if people want to keep IM accounts as separate identities, they should probably not be added to the same app and instead added to separate apps.

Also available in: Atom PDF