TODO:
Handle registration when account is disconnected right after sending registration message or when users delete & restore their account. These cases need to be thoroughly analyzed (I would like to resolve it in a separate pull).
The STR is stored in JSON, not binary (in a separate file named coniks.str), for example: {"epoch":0,"signature":[44,211,71,118,247,94,211,15,53,72,108,143,26,68,61,250,51,167,120,188,255,34,106,123,12,132,125,86,247,213,139,254,238,23,57,250,51,49,3,233,67,59,137,224,176,24,203,110,85,65,30,159,222,196,126,98,138,247,18,153,187,133,54,13]}. The reason is I think the storage space should not be a concern, and I would like to use only one format for all files (i.e., JSON).
The same for TB storage. The TB's index is stored as a part of AccountContext, and after verifying the TB is inserted as promised, it will be set to null.
This pull does:
TODO: Handle registration when account is disconnected right after sending registration message or when users delete & restore their account. These cases need to be thoroughly analyzed (I would like to resolve it in a separate pull).
Changes compare to our discussion in https://github.com/arlolra/ctypes-otr/pull/82#issuecomment-236454827:
coniks.str), for example:{"epoch":0,"signature":[44,211,71,118,247,94,211,15,53,72,108,143,26,68,61,250,51,167,120,188,255,34,106,123,12,132,125,86,247,213,139,254,238,23,57,250,51,49,3,233,67,59,137,224,176,24,203,110,85,65,30,159,222,196,126,98,138,247,18,153,187,133,54,13]}. The reason is I think the storage space should not be a concern, and I would like to use only one format for all files (i.e., JSON).AccountContext, and after verifying the TB is inserted as promised, it will be set tonull.