Copy

Task #1868

« Previous | 145 of 173 | Next »

how best to handle multiple public remote keys, fingerprints, verified statuses

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

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

0%

Category:-
Target version:0.3
Component:

Description

Figure out how best to handle duplicate keys when doing the big merge

Related issues

Related to KeySync - Task #1963: implement private key conflict handling New 09/27/2013
Duplicated by KeySync - Bug #2049: "Did not match" output New 10/10/2013
Copied to KeySync - Task #8297: how best to handle multiple public remote keys, fingerpri... New 09/12/2013

Associated revisions

Revision 5f010843
Added by Hans-Christoph Steiner over 4 years ago

add tests for sameness between adium and pidgin, refs #1888

This shows that we have work to do:

  • a lookup table for app-specific protocol names, refs #1964
  • support multiple keys per id/name, refs #1871, #1868
  • figure out zero padding problems, refs #1867

Revision 5f010843
Added by Hans-Christoph Steiner over 4 years ago

add tests for sameness between adium and pidgin, refs #1888

This shows that we have work to do:

  • a lookup table for app-specific protocol names, refs #1964
  • support multiple keys per id/name, refs #1871, #1868
  • figure out zero padding problems, refs #1867

History

#1 Updated by hans over 4 years ago

  • Subject changed from merge duplicates in the final keys to how best to handle multiple public remote keys, fingerprints, verified statuses
  • Target version set to 0.3

for now, we're just including all public remote keys and verified fingerprints. Does that always make sense?

#2 Updated by hans over 4 years ago

  • Priority changed from Normal to High
Copy

Also available in: Atom PDF