[guardian-dev] working sync for Gibberbot file-based OTR key sync
hans at guardianproject.info
Mon Apr 15 19:21:36 EDT 2013
I got the first version of the file-based key syncing working in Gibberbot!
Its just the guts without any GUI support (i.e. QRCode password scanning, bad
password handling, etc). Now when otrfileconverter outputs in Gibberbot
format, it automatically generates an AES-256-CBC encrypted file and a QRCode
for the password. The password is generated by taking the X component of the
first private key found, adding it with a 16 byte random salt, then hashing it
otrfileconverter currently outputs the QRCode to the terminal (ASCII art!) and
generates a PNG of it. Next up, the otrfileconverter-gui will also display
Right now, Gibberbot looks for a file called otr_keystore.ofcaes (Otr File
Converter A E S) in the External Storage (i.e. /sdcard). If its present, it
is automatically imported and then it deletes the original as a way to
represent that the import was successful. There will need to be GUI code
written to prompt the user to scan the QRCode password, and handle bad passwords.
I pushed the Gibberbot changes to my own repo:
And the otrfileconverter stuff is in the main repo:
Nathan, do you think you can handle the GUI changes to Gibberbot? I'm a bit
Abel, I failed at getting AES-256-GCM going, so I used AES-256-CBC to get the
ball rolling. If you think we must use GCM, then can you take that on? It
seems that openssl generates the key in a whack way, so there is a special
method in the new AES_256_GCM.java class to do it the openssl way. Maybe we
need to try skipping the openssl format, and try using M2Crypto
(openssl-based) to generate a good AES-256-GCM format.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 939 bytes
Desc: OpenPGP digital signature
More information about the Guardian-dev