This is an old revision of the document!


Lacre Ideas

Better decoupling of backend and frontend

Lacre frontend (the interface used to upload, verify and delete keys) communicates with the backend (the job actually importing keys and encrypting messages with them) via database.

This could be changed by moving all database accessing-code to the backend and exposing a simple API for the frontend to call. This API could be a Unix or TCP socket, or maybe some queue to send messages to.

Translations

We could use gettext to translate Lacre messages to different languages (for example Spanish).

Package Lacre

Use database migration framework

See Alembic

Replace custom GnuPG wrapper

Instead of using our own wrapper for GnuPG we should consider using something more thorough, like pretty-bad-protocol. (However, this project seems to be inactive since 2018…)