<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/crypto, branch 0.9_rc1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.9_rc1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.9_rc1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2011-06-29T03:06:20Z</updated>
<entry>
<title>test: fix tests after notmuch show output changes related to filenames</title>
<updated>2011-06-29T03:06:20Z</updated>
<author>
<name>Dmitry Kurochkin</name>
<email>dmitry.kurochkin@gmail.com</email>
</author>
<published>2011-05-28T22:03:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f74c4bc2f3ceedc6b6f3501c552df6c77fce9c00'/>
<id>urn:sha1:f74c4bc2f3ceedc6b6f3501c552df6c77fce9c00</id>
<content type='text'>
Adding the filename propery alongside ID and Content-type.

This makes the test suite pass again after the recent change.
</content>
</entry>
<entry>
<title>test:Improve test behaviors when --root is used</title>
<updated>2011-06-28T23:01:56Z</updated>
<author>
<name>Mark Anderson</name>
<email>ma.skies@gmail.com</email>
</author>
<published>2011-06-28T22:11:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=eb4cf465a5c179c711c15649fc90c7377850cb77'/>
<id>urn:sha1:eb4cf465a5c179c711c15649fc90c7377850cb77</id>
<content type='text'>
Change add_email_corpus, emacs_deliver_message and tests to use
$TEST_DIRECTORY instead of '..'.

This improves the behavior of the usage of --root=&lt;dir&gt;, as the
assumption of what '..' means will usually be incorrect.

Document -root option in README and update valgrind to work with
-root.
</content>
</entry>
<entry>
<title>fix sum moar typos [comments in source code]</title>
<updated>2011-06-23T22:58:39Z</updated>
<author>
<name>Pieter Praet</name>
<email>pieter@praet.org</email>
</author>
<published>2011-06-20T20:14:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8bb6f7869c4c98190f010d60409938b1c50c5968'/>
<id>urn:sha1:8bb6f7869c4c98190f010d60409938b1c50c5968</id>
<content type='text'>
Various typo fixes in comments within the source code.

Signed-off-by: Pieter Praet &lt;pieter@praet.org&gt;

Edited-by: Carl Worth &lt;cworth@cworth.org&gt; Restricted to just
source-code comments, (and fixed fix of "descriptios" to "descriptors"
rather than "descriptions").
</content>
</entry>
<entry>
<title>Render all parts of multipart/encrypted when decrypting.</title>
<updated>2011-05-27T23:22:00Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-27T10:27:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=82daf29187f84076d55df9ea35da692d200128ec'/>
<id>urn:sha1:82daf29187f84076d55df9ea35da692d200128ec</id>
<content type='text'>
The primary goal here is to keep the decrypted output as similarly
structured as undecrypted output as possible.  Now, when decrypting
parts, only the original encrypted part is replaced by the it's
decrypted content.  If this part isn't itself a multipart, then all
part numbering should remain consistent during decryption.

The only draw back here is that the useless application/pgp-encrypted
sub-part of the multipart/encrypted part is also emitted.  But this
part can be easily ignored by clients.
</content>
</entry>
<entry>
<title>Do not replace multipart/signed part with content part when doing verification.</title>
<updated>2011-05-27T23:22:00Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-27T10:27:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=54045197498f540b4ba96344073994bac13a3039'/>
<id>urn:sha1:54045197498f540b4ba96344073994bac13a3039</id>
<content type='text'>
Some folks have complained about the part renumbering that occurs when
the entire multipart/signed part is replaced with the part contents
after verification.  This is primarily because it incurs an additional
computational cost to retrieve individual parts, since verification
has to be performed again to ensure that part numbering is consistent.
This patch simply leaves the full multipart/signed part as is.

The emacs crypto test is also updated to reflect this change.
</content>
</entry>
<entry>
<title>tag signed/encrypted during notmuch new</title>
<updated>2011-05-27T23:22:00Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-26T01:01:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1d6b49561f50d6cde1b473f9887e37748e49c02c'/>
<id>urn:sha1:1d6b49561f50d6cde1b473f9887e37748e49c02c</id>
<content type='text'>
This patch adds the tag "signed" to messages with any multipart/signed
parts, and the tag "encrypted" to messages with any
multipart/encrypted parts.  This only occurs when messages are indexed
during notmuch new, so a database rebuild is required to have old
messages tagged.
</content>
</entry>
<entry>
<title>test: add crypto tests for signature verification and decryption</title>
<updated>2011-05-27T23:22:00Z</updated>
<author>
<name>Jameson Graef Rollins</name>
<email>jrollins@finestructure.net</email>
</author>
<published>2011-05-26T01:01:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=627d752501b42326b9016271de33a6cb0fa2dc8c'/>
<id>urn:sha1:627d752501b42326b9016271de33a6cb0fa2dc8c</id>
<content type='text'>
This adds a new "crypto" test script to the test suite to test
PGP/MIME signature verification and message decryption.  Included here
is a test GNUPGHOME with a test secret key (passwordless), and test
for:

  * signing/verification
  * signing/verification with full owner trust
  * verification with signer key unavailable
  * encryption/decryption
  * decryption failure with missing key
  * encryption/decryption + signing/verfifying
  * reply to encrypted message
  * verification of signature from revoked key

These tests are not expected to pass now, but will as crypto
functionality is included.
</content>
</entry>
</feed>
