4 * Bremner and dkg are co-hosting a BoF at [debconf](https://summit.debconf.org/debconf15/meeting/217/improving-privacy-and-security-for-notmuch-mail/).
6 * The meeting is Monday 2015-08-17, 1700-1800 CET
8 * Video streaming should be [available](https://wiki.debconf.org/wiki/DebConf15/Videostream/Amsterdam)
14 Moving parts for secure e-mail
16 * libxapian (C++, full text search)
17 * libgmime (C, glib, RFC822+MIME library)
18 * libnotmuch (C and C++)
19 * /usr/bin/notmuch (C)
21 * Emacs UI (emacs lisp)
24 * Alot / nmbug / nmbug-status (python)
28 * notmuch web (Haskell)
30 Security and privacy concerns
31 -----------------------------
32 * privacy leaks rendering messages
33 * wrong key selection during composition
34 * reply (message mode defaults)
36 * message-id collisions
37 * webmail authentication/authorization (multiple users?)
38 * webmail message escaping (XSS, etc)
40 * terminal escape sequences
42 * reproducible builds:
43 [sphinx man pages](https://reproducible.debian.net/rb-pkg/testing/amd64/notmuch.html)
45 ### usability as security?
47 * indexing encrypted mail
48 * Memory Hole protected headers
49 * key selection indicators during composition
55 * based on moving part
62 -------------------------
66 * Improving the security of the Emacs MML mime composer
67 * Searching of GPG encrypted mail
68 * Auditing and fixing "webbug" style problems in front ends
73 * S/MIME signatures and encryption
75 * integration with other keyrings
76 * signature only (easyish) versus encryption (more work)
77 * Improving the security of the Emacs MML mime composer
78 * automated "encrypt-when-i-have-keys-available" mode or other convenience functions?
79 * can an adversary force signatures based on quoted text?
80 * generate memory-hole-style messages
81 * Searching of GPG encrypted mail
82 * possible implementation mechanism: "notmuch reindex --with-filter=decrypt"
83 * Auditing and fixing "webbug" style problems in front ends
84 * can we instruct emacs to restrict all network access from notmuch?
85 * what other frontends might call out to the network?
86 * Making notmuch build reproducibly
87 * https://reproducible.debian.net/rb-pkg/unstable/amd64/notmuch.html
88 * Protect against spoofed signature verification?
89 * how do we deal with multipart messages where only a subtree is signed?
90 * are other sorts of spoofing possible?
91 * read and display memory-hole-style messages
92 * "safe" ways to display html parts (e.g. without text/plain alternatives)