holger krekel

split keyhandle out of chainstate

1

Currently OwnState's KeygenEntry redundantly keeps track of keyhandles although the keyhandle is computed from ``keydata`` which is also contained in KeygenEntry. Remove the redundancy which probably also helps #32

mailman3 integration

2

[mailman3-core](https://gitlab.com/mailman/mailman/tree/master) is implemented in a modular fashion in python. We should be able to add autocrypt encryption either by integrating directly with mailman3's pipelines or by integrating with in/out filters...

For MUAs operating on an offlineimap/isync/fetchmail imap-synced copy of mails it might be nice if py-autocrypt could create and maintain a parallel directory structure with all mails in the clear...

Some things are quite annoying to do reliably with gpg/gpg2, like getting the openpgp4 fingerprint of ac-transmitted keydata. I suspect that also #24 will be annoying to do with gpg...

- Find out how to recognize requests for DSNs and how a response needs to look like - implement it for the bot

integrate pgpy as a new (possibly default) backend

3

There is a separate https://github.com/juga0/pyac effort which implements Autocrypt and is based on https://github.com/SecurityInnovation/PGPy instead of gpg like this repository. Here are a few things i'd like to see before...

Not sure when but in general i guess it makes sense to split the current codebase into two packages: the core python API and the command line tool on top...

Add support for generating and receiving Autocrypt Setup Messages, test it with enigmail, Delta.chat and K-9. Probably depends on #22

As suggested by @nwalfield it's probably better to use the ``--status-fd`` option with gpg/gpg2 which is supposedly more stable than parsing gpg/gpg2's output.

Fall back to FTS4 if FTS5 is not available

3

got this with version 0.21.1 from pypi. twitter-to-sqlite auth worked but then "twitter-to-sqlite user-timeline USER.db" produced a tracekback ending in "no such module: FTS5".