Copy

Bug #1867

« Previous | 41 of 41 | Next »

otr.private_key format is sometimes improperly padded with leading zeros

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

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

0%

Category:-
Target version:0.3
Component:

Description

Sometimes, the resulting `otr.private_key` file has different 00 leading padding than the original format. It seems to only affect the g and x numbers, but that could just be because of my small sample set. The original format sometimes adds 00 padding to the beginning of some numbers, so its not entirely wrong, just sometimes.

-  (g #65ABF36AAF6E1F28F26031DB5A9BFBDB76292F9B9507C94D2F2A57CC...
+  (g #0065ABF36AAF6E1F28F26031DB5A9BFBDB76292F9B9507C94D2F2A57CC...

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

  • Target version set to 0.3
Copy

Also available in: Atom PDF