<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/mime-node.c, branch 0.16_rc1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.16_rc1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.16_rc1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2013-04-14T22:49:16Z</updated>
<entry>
<title>cli: mime node: fix compiler warning when building against gmime 2.4</title>
<updated>2013-04-14T22:49:16Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2013-04-06T11:47:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d2c881867ea4858f4a4785af5ec5d4223e5e0257'/>
<id>urn:sha1:d2c881867ea4858f4a4785af5ec5d4223e5e0257</id>
<content type='text'>
commit d487ef9e58bcd193118f19f771d5ef3984616be5
Author: Jani Nikula &lt;jani@nikula.org&gt;
Date:   Sat Mar 30 15:53:16 2013 +0200

    cli: mime node: abstract decryption and signature verification

introduced a compiler warning, reported by Mark Walters, when building
against gmime 2.4:

mime-node.c:224:9: warning: assignment discards ‘const’ qualifier from
pointer target type [enabled by default]

Pass the non-const signature validity to the destructor to fix this.
</content>
</entry>
<entry>
<title>cli: mime node: abstract decryption and signature verification</title>
<updated>2013-04-01T19:39:33Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2013-03-30T13:53:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d487ef9e58bcd193118f19f771d5ef3984616be5'/>
<id>urn:sha1:d487ef9e58bcd193118f19f771d5ef3984616be5</id>
<content type='text'>
The code filled with #ifdef GMIME_ATLEAST_26 is difficult to
read. Abstract the decryption and signature verification into
functions, with separate implementations for GMime 2.4 and 2.6, to
clarify the code.

There should be no functional changes.
</content>
</entry>
<entry>
<title>Avoid potentially dereferencing a NULL pointer</title>
<updated>2012-09-27T15:52:34Z</updated>
<author>
<name>Justus Winter</name>
<email>4winter@informatik.uni-hamburg.de</email>
</author>
<published>2012-09-24T15:21:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b6b08e40b38b098e796c2846c150befc8cc2c350'/>
<id>urn:sha1:b6b08e40b38b098e796c2846c150befc8cc2c350</id>
<content type='text'>
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-&gt;part is valid.

Found using the clang static analyzer.

Signed-off-by: Justus Winter &lt;4winter@informatik.uni-hamburg.de&gt;
</content>
</entry>
<entry>
<title>cli: use new notmuch_crypto_get_context in mime-node.c</title>
<updated>2012-06-10T23:09:42Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2012-05-26T18:45:46Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e04b18cf3624e1ba29a45cd1f15715e1da244021'/>
<id>urn:sha1:e04b18cf3624e1ba29a45cd1f15715e1da244021</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>cli: new crypto verify flag to handle verification</title>
<updated>2012-06-10T23:09:09Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2012-05-26T18:45:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b2c8fdee53a1b06dd19fafe23e53ac8555d294af'/>
<id>urn:sha1:b2c8fdee53a1b06dd19fafe23e53ac8555d294af</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>cli: modify mime_node_context to use the new crypto struct</title>
<updated>2012-06-10T23:08:56Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2012-05-26T18:45:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=90822ffdb830060c6f1d73ad1f6c7964c9f20ad4'/>
<id>urn:sha1:90822ffdb830060c6f1d73ad1f6c7964c9f20ad4</id>
<content type='text'>
This simplifies some more interfaces.
</content>
</entry>
<entry>
<title>cli: modify mime_node_open to take new crypto struct as argument</title>
<updated>2012-06-10T23:06:48Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2012-05-26T18:45:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=429ebf5d20a943fb520d7321c5dde721265b0155'/>
<id>urn:sha1:429ebf5d20a943fb520d7321c5dde721265b0155</id>
<content type='text'>
This simplifies the interface considerably.
</content>
</entry>
<entry>
<title>cli: use new typedef to deal with gmime 2.4/2.6 context incompatibility</title>
<updated>2012-06-10T23:04:50Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2012-05-26T18:45:40Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=25c3140e13698b147baedd99b2d6f8775c67de07'/>
<id>urn:sha1:25c3140e13698b147baedd99b2d6f8775c67de07</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Handle errors in mime_node_open</title>
<updated>2012-03-11T01:25:19Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-03-06T18:26:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=353577ad5733b78b71d93c9bdbaae0b062d32331'/>
<id>urn:sha1:353577ad5733b78b71d93c9bdbaae0b062d32331</id>
<content type='text'>
</content>
</entry>
<entry>
<title>mime node: Record depth-first part numbers</title>
<updated>2012-01-25T11:19:22Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-01-23T23:33:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a66e65d604c5e658daa97acbb9d0487788863521'/>
<id>urn:sha1:a66e65d604c5e658daa97acbb9d0487788863521</id>
<content type='text'>
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.
</content>
</entry>
</feed>
