notmuch/mime-node.c, branch 0.15.2

Avoid potentially dereferencing a NULL pointer

2012-09-27T15:52:34Z

GMIME_IS_MULTIPART and GMIME_IS_MESSAGE both handle NULL pointers gracefully, but the G_OBJECT_TYPE used in the error handling block dereferences it without checking it first. Fix this by checking whether parent->part is valid. Found using the clang static analyzer. Signed-off-by: Justus Winter <4winter@informatik.uni-hamburg.de>

cli: use new notmuch_crypto_get_context in mime-node.c

2012-06-10T23:09:42Z

This has the affect of lazily creating the crypto contexts only when needed. This removes code duplication from notmuch-show and notmuch-reply, and should speed up these functions considerably if the crypto flags are provided but the messages don't have any cryptographic parts.

cli: new crypto verify flag to handle verification

2012-06-10T23:09:09Z

Use this flag rather than depend on the existence of an initialized gpgctx, to determine whether we should verify a multipart/signed. We will be moving to create the ctx lazily, so we don't want to depend on it being previously initialized if it's not needed.

cli: modify mime_node_context to use the new crypto struct

2012-06-10T23:08:56Z

This simplifies some more interfaces.

cli: modify mime_node_open to take new crypto struct as argument

2012-06-10T23:06:48Z

This simplifies the interface considerably.

cli: use new typedef to deal with gmime 2.4/2.6 context incompatibility

2012-06-10T23:04:50Z

gmime 2.4 defines GMimeCipherContext, while 2.6 defines GMimeCryptoContext. typedef them both to notmuch_crypto_context_t to cover this discrepancy and remove a bunch of #ifdefs.

Handle errors in mime_node_open

2012-03-11T01:25:19Z

mime node: Record depth-first part numbers

2012-01-25T11:19:22Z

This makes the part numbers readily accessible to formatters. Hierarchical part numbering would be a more natural and efficient fit for MIME and may be the way to go in the future, but depth-first numbering maintains compatibility with what we currently do.

Add compatibility with gmime 2.6

2012-01-21T12:52:34Z

There are lots of API changes in gmime 2.6 crypto handling. By adding preprocessor directives, it is however possible to add gmime 2.6 compatibility while preserving compatibility with gmime 2.4 too. This is mostly based on id:"8762i8hrb9.fsf@bookbinder.fernseed.info". This was tested against both gmime 2.6.4 and 2.4.31. With gmime 2.4.31, the crypto tests all work fine (as expected). With gmime 2.6.4, one crypto test is currently broken (signature verification with signer key unavailable), most likely because of a bug in gmime which will hopefully be fixed in a future version.

Utility function to seek in MIME trees in depth-first order.

2011-12-26T02:21:04Z

This function matches how we number parts for the --part argument to show. It will allow us to jump directly to the desired part, rather than traversing the entire tree and carefully tracking whether or not we're "in the zone".