<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/crypto.c, branch debian/0.24.2-2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.24.2-2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.24.2-2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2016-06-05T11:32:17Z</updated>
<entry>
<title>Use https instead of http where possible</title>
<updated>2016-06-05T11:32:17Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-06-02T16:26:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6a833a6e83865f6999707cc30768d07e1351c2cb'/>
<id>urn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb</id>
<content type='text'>
Many of the external links found in the notmuch source can be resolved
using https instead of http.  This changeset addresses as many as i
could find, without touching the e-mail corpus or expected outputs
found in tests.
</content>
</entry>
<entry>
<title>cli: crypto: S/MIME verification support</title>
<updated>2016-01-29T21:45:46Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-08-16T17:41:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2355f1522ae77a1012ca3ef08d97098a5951d142'/>
<id>urn:sha1:2355f1522ae77a1012ca3ef08d97098a5951d142</id>
<content type='text'>
notmuch-show --verify will now also process S/MIME multiparts if
encountered. Requires gmime-2.6 and gpgsm.

Based on work by Jameson Graef Rollins &lt;jrollins@finestructure.net&gt;.
</content>
</entry>
<entry>
<title>cli: let the user know which protocol is unknown or unsupported</title>
<updated>2015-12-30T15:28:30Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-12-14T13:38:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=190f69169dc5c2ee12dcf077ead7f3fac4d9d88b'/>
<id>urn:sha1:190f69169dc5c2ee12dcf077ead7f3fac4d9d88b</id>
<content type='text'>
The current error message is not helpful.
</content>
</entry>
<entry>
<title>crypto: make crypto ctx initialization an array</title>
<updated>2015-12-30T15:28:30Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-12-14T13:38:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cb494f72f398bb0898030a1225f9ef6da557e959'/>
<id>urn:sha1:cb494f72f398bb0898030a1225f9ef6da557e959</id>
<content type='text'>
Make it trivial to add handlers for new protocols without duplicating
code. No functional changes.
</content>
</entry>
<entry>
<title>crypto: refactor context creation to facilitate further work</title>
<updated>2015-12-30T15:28:30Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-12-14T13:38:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4419069472195615ad856c6d46c82f2beb33202f'/>
<id>urn:sha1:4419069472195615ad856c6d46c82f2beb33202f</id>
<content type='text'>
Let the context creation functions decide how to handle multiple calls
and cache the crypto context. No functional changes.
</content>
</entry>
<entry>
<title>cli/lib: remove support for GMime 2.4</title>
<updated>2015-08-26T23:01:45Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-08-16T15:33:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=005c2f0df17de8afdf9f67b923d26f2358236171'/>
<id>urn:sha1:005c2f0df17de8afdf9f67b923d26f2358236171</id>
<content type='text'>
It's becoming a maintenance burden to do anything things with the
crypto glue code twice, once for 2.4 and once for 2.6. I don't have
any 2.4 version available to test on my development machine anymore,
so the 2.4 specific code paths are likely not very well tested.
</content>
</entry>
<entry>
<title>CLI: set up infrastructure to make path to gpg configurable.</title>
<updated>2015-03-09T07:19:28Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2014-12-09T20:01:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=21ecd7369aa2aa24d26775c3fe5edcb437914774'/>
<id>urn:sha1:21ecd7369aa2aa24d26775c3fe5edcb437914774</id>
<content type='text'>
GMIME takes a path to gpg, but we hardcode that path.  In this commit
we set up argument passing and option storage to allow this path to
specified in the top level notmuch command.
</content>
</entry>
<entry>
<title>crypto: return NULL cryptoctx if protocol string is empty.</title>
<updated>2013-07-20T12:13:48Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2013-07-19T15:36:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=348437243c861cc355f10e548a7a973a60299a25'/>
<id>urn:sha1:348437243c861cc355f10e548a7a973a60299a25</id>
<content type='text'>
Badly formed messages that don't specify a protocol in
signed/encrypted parts, end up with a protocol of NULL.  strcasecmp in
notmuch_crypto_get_context then segfaults when trying to check it
against known protocols.  If the protocol is NULL, just return an
empty context immediately (with appropriate message.)
</content>
</entry>
<entry>
<title>cli: crypto: abstract gpg context creation for clarity</title>
<updated>2013-04-01T19:39:22Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2013-03-30T13:53:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8c6fd797952d38e03d46fd6b57bd6a1a63474de8'/>
<id>urn:sha1:8c6fd797952d38e03d46fd6b57bd6a1a63474de8</id>
<content type='text'>
The code filled with #ifdef GMIME_ATLEAST_26 is difficult to
read. Abstract gpg context creation into a function, with separate
implementations for GMime 2.4 and 2.6, to clarify the code.

There should be no functional changes.
</content>
</entry>
<entry>
<title>cli: crypto: tell gmime to use gpg-agent</title>
<updated>2013-03-02T14:41:24Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2013-02-27T07:40:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c5c5770b22dfdb930558979668756cf51a7cc482'/>
<id>urn:sha1:c5c5770b22dfdb930558979668756cf51a7cc482</id>
<content type='text'>
For decryption, we expect there to be a functioning gpg-agent, and we
want gpg to talk to it for any needed credentials. There's a gmime
function to declare that: g_mime_gpg_context_set_use_agent() [1], [2].
Start using it.

I had gpg-agent running, but gpg "use-agent" configuration option
disabled. This resulted in an error message from 'notmuch show':

  Failed to decrypt part: Canceled.

and json had this:

  "encstatus" : [ { "status" : "bad" } ]

One could argue the "use-agent" option should be enabled, but I'd like
to use the agent only as a last resort. I think that's irrelevant
though. There's a gmime function to declare what we expect, so we
should use it. Conveniently it also fixes the problem in a user
friendly way.

[1] http://git.gnome.org/browse/gmime/commit/?id=ed985397843a9da3745a8b5de3d1d652acd24724
[2] https://bugzilla.gnome.org/show_bug.cgi?id=651826
</content>
</entry>
</feed>
