notmuch, branch 0.25.3thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.25.32017-12-09T01:08:21Zdebian: add changelog stanza for 0.25.3-12017-12-09T01:08:21ZDavid Bremnerdavid@tethera.net2017-12-09T01:08:21Zurn:sha1:ae55a86639f86ad1b547e961f71b1bde2180752ddebian: disable gdb on alpha2017-12-09T01:05:25ZDavid Bremnerdavid@tethera.net2017-12-09T01:05:25Zurn:sha1:8520bfb9f4eefabee9cdeb4a6e6e7891ce9fdffe
gdb seems to be broken on more architectures than it works :(.
INSTALL: suggest gmime-3.x2017-12-09T01:01:17ZDavid Bremnerdavid@tethera.net2017-12-09T01:01:17Zurn:sha1:8e69663a8b4b9d1cce4faf7b55514ec3efe2499e
Since we deprecated support for GMime 2.6...
debian: add versioned depends on libgmime2017-12-09T00:59:45ZDavid Bremnerdavid@tethera.net2017-12-09T00:59:45Zurn:sha1:7a1d1912e7a8d11d1dbaf6f5e8524b841601946fNEWS: news for 0.25.32017-12-09T00:57:28ZDavid Bremnerdavid@tethera.net2017-12-09T00:56:02Zurn:sha1:000bbc73ff135fa588ba4e57c03489d87a13761cversion: bump to 0.25.32017-12-09T00:47:25ZDavid Bremnerdavid@tethera.net2017-12-09T00:47:25Zurn:sha1:ecb5668178c813fb6f1014d4ae9919655e2a17edtest/emacs: add exploit mitigation test2017-12-09T00:36:20ZDavid Bremnerdavid@tethera.net2017-12-06T01:17:58Zurn:sha1:151b2c37472ddca1a974044c77108c784a6bc79a
This test will pass if either the notmuch show mitigation code is
working correctly, or upstream emacs mime handling code has it's own
fix for https://bugs.gnu.org/28350.
emacs: letf enriched-decode-display-prop for text/enriched display2017-12-09T00:35:41ZTomi Ollilatomi.ollila@iki.fi2017-12-06T01:17:57Zurn:sha1:f55e9a3bdaadb6d7db7321d0aee5de642743651d
Dynamically bind enriched-decode-display-prop when inserting
text/enriched part. This complements commit 9b0582383833 for
emacs versions before 24.4 which do not have advice-add
functionality.
Since emacs 25.3 this particular bug is fixed.
crypto: signature verification reports valid User IDs2017-12-09T00:35:18ZDaniel Kahn Gillmordkg@fifthhorseman.net2017-12-08T20:09:46Zurn:sha1:cb855d8a9d24084d0965790782c1ce04b82aa9ca
When i'm trying to understand a message signature, i care that i know
who it came from (the "validity" of the identity associated with the
key), *not* whether i'm willing to accept the keyholder's other
identity assertions (the "trust" associated with the certificate).
We've been reporting User ID information based on the "trust"
associated with the certificate, because GMime didn't clearly expose
the validity of the User IDs.
This change relies on fixes made in GMime 3.0.3 and later which
include https://github.com/jstedfast/gmime/pull/18.
debian: changelog for 0.25.2-12017-11-06T00:06:23ZDavid Bremnerdavid@tethera.net2017-11-06T00:06:23Zurn:sha1:83f266136369452b859393429b8530efac2e09fb