Disroot
/
gpg-lacre
9
15
Fork 4
Code Issues 29 Pull Requests 1 Releases 2 Wiki Activity

add wishes for the future: advanced filters, BerkeleyDB-based identity registry

pfm 2021-05-30 10:15:02 +00:00
parent cb9351f0ce
commit 2375ec3cca
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Ideas.md

@ -3,4 +3,8 @@
1. setting up a directory with a single key,
2. calling Lacre from command-line, feeding its standard-input with a message,
3. verifying that the result is properly encoded and is still a valid email.
* Installation of gpg-mailgate used to be a manual, error-prone process. We can change it into at least semi-automatic process supported by helper scripts.
* Installation of gpg-mailgate used to be a manual, error-prone process. We can change it into at least semi-automatic process supported by helper scripts.
# Future
* We could migrate from a *simple content filters* to *advanced content filters* in the future. This would improve performance.
* Identities could be stored in Berkeley DB or another file-based database (gdbm, ndbm). Berkeley DB is quite advanced though and often used by mail infrastructure (e.g. aliases databases), so this would make Lacre more natural for mail administrators. Also, a MySQL or MariaDB dependency is quite heavy. (We could use Btree or Hash for identities and Queue for a queue of identities submitted via web interface or over incoming email addressed to register@ virtual account).