[guardian-dev] Gibberbot keystore format

[Miron]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14/08/12 12:59, Hans-Christoph Steiner wrote:
> 
> I was thinking about this a little more.  If I recall, you're in
> the process of integrating SQLCipher into Gibberbot.  Then I think
> it makes sense to switch the keystore over to a SQLCipher database,
> then allow Gibberbot to import/export using a well-known file
> format.  If that's what you were proposing before, I totally missed
> that.

Yup, sorry if I was unclear.

> 
> Gibberbot should at minimum be able to read its own file format,
> but if it wasn't much work, then it would make sense to add direct 
> importing of Pidgin files.  Reading the Pidgin file format is 
> documented and implemented in the OTRFileConverter, so it could be 
> pretty easy.

The only issue is that Pidgin doesn't have a pubkey column (only
fingerprint).  Should we just add a column to it?  I can check if
Pidgin will ignore the extra column.

> 
> Then we'd just need to figure out how the import/export process 
> actually works, mostly in terms of how to securely copy the files 
> around.

I was thinking of piping directly into APG for export (APG will let
you email it).  We can also register a specific extension so that on
decryption APG automatically routes it to Gibberbot.  I have to check
if this is all done securely - i.e. that APG does not store plaintext
on flash.

> 
> .hc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFQKyR2/VxauoqzwoERAgMGAJ9VIPPNFtHWfjkVkbjAjNSOnrKJAwCfWVG5
6OEXu1wVwu434dVEocD6U8g=
=L87C
-----END PGP SIGNATURE-----