X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=meetings%2Fhd2015.mdwn;h=add26ca530ec526242755a490d59b97a9bad8d71;hb=42bf578717c5ac63b818876555929bcc842c8523;hp=fa96aed01162d763e54217f33f47546f509f5a21;hpb=7ad1dd0a2c096b991a2bc97bf9e53c7c0f1125b7;p=notmuch-wiki diff --git a/meetings/hd2015.mdwn b/meetings/hd2015.mdwn index fa96aed..add26ca 100644 --- a/meetings/hd2015.mdwn +++ b/meetings/hd2015.mdwn @@ -20,30 +20,37 @@ Moving parts for secure e-mail * GnuPG (C) * Emacs UI (emacs lisp) * notmuch-emacs - * mml-mode + * mml-mode, mm multimedia rendering library * Alot / nmbug / nmbug-status (python) * python-bindings * webmail: * noservice (Clojure) * notmuch web (Haskell) -Security concerns ------------------ -* wrong key selection during composition -* reply (message mode defaults) -* inline PGP +Security and privacy concerns +----------------------------- +* privacy leaks rendering messages * message-id collisions -* webmail authentication/authorization (muliple users?) +* Oops I just sent... + * wrong key selection during composition + * reply (message mode defaults) +* inline PGP + +* webmail authentication/authorization (multiple users?) * webmail message escaping (XSS, etc) * shell injection * terminal escape sequences * S/MIME support + * signatures + * encryption +* reproducible builds: + [sphinx man pages](https://reproducible.debian.net/rb-pkg/testing/amd64/notmuch.html) ### usability as security? * indexing encrypted mail * Memory Hole protected headers -* key selection indicators during compositoin +* key selection indicators during composition Breakout sessions @@ -58,16 +65,6 @@ Reportbacks ------------------------- -proposed session: ---------- -One of (at least my) primary motivations for working on Notmuch is reducing my dependence on cloud services, and supporting the secure sending and receiving of signed and encrypted mail. Like any realworld piece of software, notmuch is far from perfect, and several areas related to privacy and security could clearly be improved. During this BoF we'd like to plan out some topics to work on in followup hacking sessions. Anyone is welcome, even if they don't feel like hacking on notmuch. Potential topics of discussion andhacking include: - * S/MIME signatures and encryption - * Improving the security of the Emacs MML mime composer - * Searching of GPG encrypted mail - * Auditing and fixing "webbug" style problems in front ends - * Making notmuch build reproducibly - ---------- more complete agenda: