notmuch/test, branch 0.25.3 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.25.3 2017-12-09T00:36:20Z test/emacs: add exploit mitigation test 2017-12-09T00:36:20Z David Bremner david@tethera.net 2017-12-06T01:17:58Z urn: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. crypto: signature verification reports valid User IDs 2017-12-09T00:35:18Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-12-08T20:09:46Z urn: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. emacs: convert remaining format-versions from 3 to 4 2017-07-18T09:57:26Z David Bremner david@tethera.net 2017-07-17T15:06:11Z urn:sha1:1d82110f8397e413d1e000b5a2aa99a2b0995e6d This is needed for consistent beheviour between notmuch built against gmime-2.6 and gmime-3.0 w.r.t. error reporting. Fix orthography 2017-07-18T09:50:44Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-07-17T22:16:02Z urn:sha1:87bdfbc91f65cb1031ef0ac8a804759f2061ac10 emacs: change default for notmuch-crypto-process-mime to t 2017-07-15T12:11:32Z David Bremner david@tethera.net 2017-07-12T10:48:18Z urn:sha1:f1bcb6b7c2c568adcdfd4503522cfbccc4699665 There are some cases like remote usage where this might cause problems, but those users can easily customize the variable. The inconvenience seems to be outweighed by the security benefit for most users. config: deprecate/drop crypto.gpg_path under gmime 2.6/3.0 2017-07-15T00:23:52Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-07-14T13:12:00Z urn:sha1:e142de643d3bb4354f70e1490a97b491d1116e95 gmime 3.0 no longer offers a means to set the path for gpg. Users can set $PATH anyway if they want to pick a differently-installed gpg (e.g. /usr/local/bin/gpg), so this isn't much of a reduction in functionality. The one main difference is for people who have tried to use "gpg2" to make use of gpg 2.1, but that isn't usefully co-installable anyway. Add additional munged reply-to tests 2017-07-15T00:23:52Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-07-14T20:14:23Z urn:sha1:8492298a613e8e666d0f3054dadcb98b72a65ae4 The reply-to munging code might behave differently whether there's an exact match on the strings or not, or whether the string is a raw addr-spec instead of an name-addr. These tests cover those variations (i also had to tweak json output further below when this new test was added). Ensure that "notmuch reply" succeeds during testing. 2017-07-15T00:23:52Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-07-14T20:14:22Z urn:sha1:23a4d09773ebdb8b3b5d45b6fa5196190228f52d In some (bad!) cases, "notmuch reply" might fail, or might even segfault. If this happens, it indicates a bug, and the test suite should notice it. test/crypto: mark extra space in userid as a bug in gmime-2.6 2017-07-14T20:58:09Z David Bremner david@tethera.net 2017-06-03T00:29:25Z urn:sha1:a58c75fdf6120aa3861e95a4a61fa268dee6a690 I can't see the space in the output of gpg -K --with-colons cli: add space separator for keyword, string, and int arguments 2017-07-12T20:46:29Z David Bremner david@tethera.net 2017-07-01T15:18:45Z urn:sha1:a32dd81a55a5d745dbf840b42d03e835a4e1e45c Defer the complication of optional boolean arguments for later (never?).