notmuch/util, branch 0.29

util/crypto: add information about the payload part

2019-05-29T11:02:45Z

When walking the MIME tree, if we discover that we are at the cryptographic payload, then we would like to record at least the Subject header of the current MIME part. In the future, we might want to record many other headers as well, but for now we will stick with just the Subject. See https://dkg.fifthhorseman.net/blog/e-mail-cryptography.html#cryptographic-envelope for more description of the Cryptographic Payload vs. the Cryptographic Envelope. Signed-off-by: Daniel Kahn Gillmor

util/crypto: _notmuch_message_crypto: tracks message-wide crypto state

2019-05-26T11:20:23Z

E-mail encryption and signatures reported by notmuch are at the MIME part level. This makes sense in the dirty details, but for users we need to have a per-message conception of the cryptographic state of the e-mail. (see https://dkg.fifthhorseman.net/blog/e-mail-cryptography.html for more discussion of why this is important). The object created in this patch is a useful for tracking the cryptographic state of the underlying message as a whole, based on a depth-first search of the message's MIME structure. This object stores a signature list of the message, but we don't handle it yet. Further patches in this series will make use of the signature list.

util: add unicode_word_utf8

2019-05-25T09:51:12Z

This originally use Xapian::Unicode::is_wordchar, but that forces clients to link directly to libxapian, which seems like it might be busywork if nothing else.

util/crypto: improve comment

2019-05-07T09:41:28Z

The comment line here lingers from when we were using some fancy version checking about session keys. Correct it to match the current state. Signed-off-by: Daniel Kahn Gillmor

util/gmime-extra: add g_mime_stream_gzfile_{new, open}

2019-05-03T10:48:38Z

These are usable as standard GMime streams, and transparently decompress gzipped files.

gmime-cleanup: pass NULL as default GMimeParserOptions

2019-05-03T09:58:00Z

This is a functional change, not a straight translation, because we are no longer directly invoking g_mime_parser_options_get_default(), but the GMime source has indicated that the options parameter for g_mime_parser_construct_message() is "nullable" since upstream commit d0ebdd2ea3e6fa635a2a551c846e9bc8b6040353 (which itself precedes GMime 3.0). Signed-off-by: Daniel Kahn Gillmor

gmime-cleanup: pass NULL arguments explicitly where GMime 3.0 expects it

2019-05-03T09:57:27Z

Several GMime 2.6 functions sprouted a change in the argument order in GMime 3.0. We had a compatibility layer here to be able to handle compiling against both GMime 2.6 and 3.0. Now that we're using 3.0 only, rip out the compatibility layer for those functions with changed argument lists, and explicitly use the 3.0 argument lists. Signed-off-by: Daniel Kahn Gillmor

gmime-cleanup: use GMime 3.0 function names

2019-05-03T09:57:16Z

Signed-off-by: Daniel Kahn Gillmor

gmime-cleanup: use GMime 3.0 data types

2019-05-03T09:57:06Z

Signed-off-by: Daniel Kahn Gillmor

gmime-cleanup: drop unused gmime #defines and simplify g_mime_init ()

2019-05-03T09:56:58Z

Several of these #defines were not actually used in the notmuch codebase any longer. And as of GMime 3.0, g_mime_init takes no arguments, so we can also drop the bogus RFC2047 argument that we were passing and then #defining away. signed-off-by: Daniel Kahn Gillmor