<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T355-smime.sh, branch 0.35</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.35</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.35'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2021-06-26T16:07:47Z</updated>
<entry>
<title>cli/show: produce "email" element in sigstatus</title>
<updated>2021-06-26T16:07:47Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2021-05-27T01:44:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8c29a5da096b0314c6cca8889b740b79a9a548ed'/>
<id>urn:sha1:8c29a5da096b0314c6cca8889b740b79a9a548ed</id>
<content type='text'>
When the certificate that signs a message is known to be valid, GMime
is capable of reporting on the e-mail address embedded in the
certificate.

We pass this information along to the caller of "notmuch show", as
often only the e-mail address of the certificate has actually been
checked/verified.

Furthermore, signature verification should probably at some point
compare the e-mail address of the caller against the sender address of
the message itself.  Having to parse what gmime thinks is a "userid"
to extract an e-mail address seems clunky and unnecessary if gmime
already thinks it knows what the e-mail address is.

See id:878s41ax6t.fsf@fifthhorseman.net for more motivation and discussion.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>test: source $NOTMUCH_SRCDIR/test/test-lib-emacs.sh</title>
<updated>2021-06-03T12:29:27Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2021-05-23T07:34:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=572af2795007464ffbf9cd4656e0e5736d78d362'/>
<id>urn:sha1:572af2795007464ffbf9cd4656e0e5736d78d362</id>
<content type='text'>
Sourcing test-lib.sh will cd to TMP_DIRECTORY, so
relative path in $0 will not work in previous version
 . $(dirname "$0")/test-lib-emacs.sh

Now individual test scripts -- e.g. ./test/T310-emacs.sh
will work.
</content>
</entry>
<entry>
<title>test: split emacs functionality to its own file</title>
<updated>2021-05-17T10:29:04Z</updated>
<author>
<name>Felipe Contreras</name>
<email>felipe.contreras@gmail.com</email>
</author>
<published>2021-05-15T20:47:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=92454bc0935604f4a623e75dec9506c0283eee70'/>
<id>urn:sha1:92454bc0935604f4a623e75dec9506c0283eee70</id>
<content type='text'>
This way it's easier to identify the tests that do require emacs stuff.

Signed-off-by: Felipe Contreras &lt;felipe.contreras@gmail.com&gt;
</content>
</entry>
<entry>
<title>test: add external prereqs to many emacs tests</title>
<updated>2021-05-02T00:15:27Z</updated>
<author>
<name>Felipe Contreras</name>
<email>felipe.contreras@gmail.com</email>
</author>
<published>2021-05-01T11:54:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fe9616aef19a1584de550ea536dfc7b42a13636a'/>
<id>urn:sha1:fe9616aef19a1584de550ea536dfc7b42a13636a</id>
<content type='text'>
The tests fail otherwise.

Signed-off-by: Felipe Contreras &lt;felipe.contreras@gmail.com&gt;
</content>
</entry>
<entry>
<title>T355: specify hash algorithm explicitly</title>
<updated>2020-08-08T19:04:27Z</updated>
<author>
<name>Đoàn Trần Công Danh</name>
<email>congdanhqx@gmail.com</email>
</author>
<published>2020-08-03T15:40:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f5ae8040b3ebba8ffa1be485c3a74397df98138e'/>
<id>urn:sha1:f5ae8040b3ebba8ffa1be485c3a74397df98138e</id>
<content type='text'>
On some systems (notably, the one shipped with LibreSSL),
default fingerprint digest algorithm is SHA256.

On other systems, users can change default digest algorithm by changing
default_md in /etc/ssl/default_md.

Let's ask openssl to provide us specific algorithm to make the test
more deterministic.

Signed-off-by: Đoàn Trần Công Danh &lt;congdanhqx@gmail.com&gt;
</content>
</entry>
<entry>
<title>test: mark two tests broken on machines with 32 bit time_t</title>
<updated>2020-06-27T01:16:51Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-06-24T14:32:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b46d842782527b206e139edd00ab1ac896b5a23b'/>
<id>urn:sha1:b46d842782527b206e139edd00ab1ac896b5a23b</id>
<content type='text'>
I haven't traced the code path as exhaustively for the SMIME test, but
the expiry date in question is larger then representable in a signed
32 bit integer.
</content>
</entry>
<entry>
<title>smime: Index cleartext of envelopedData when requested</title>
<updated>2020-05-23T01:12:00Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-12T22:29:39Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6cdf4b7e38000c6d0a14ff04ab71f7c7e60835ec'/>
<id>urn:sha1:6cdf4b7e38000c6d0a14ff04ab71f7c7e60835ec</id>
<content type='text'>
Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>smime: Pass PKCS#7 envelopedData to node_decrypt_and_verify</title>
<updated>2020-05-23T01:11:51Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-12T22:29:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cb88b51fe55fcb01235747d4b94072fa6efd501c'/>
<id>urn:sha1:cb88b51fe55fcb01235747d4b94072fa6efd501c</id>
<content type='text'>
This change means we can support "notmuch show --decrypt=true" for
S/MIME encrypted messages, resolving several outstanding broken tests,
including all the remaining S/MIME protected header examples.

We do not yet handle indexing the cleartext of S/MIME encrypted
messages, though.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>cli/reply: Ignore PKCS#7 wrapper parts when replying</title>
<updated>2020-05-23T01:11:25Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-12T22:29:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1b9f4a9863003955e6a757a6eeb8b6926d60c896'/>
<id>urn:sha1:1b9f4a9863003955e6a757a6eeb8b6926d60c896</id>
<content type='text'>
When composing a reply, no one wants to see this line in the proposed
message:

    Non-text part: application/pkcs7-mime

So we hide it, the same way we hide PGP/MIME cruft.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>cli/show: If a leaf part has children, show them instead of omitting</title>
<updated>2020-05-23T01:11:17Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2020-05-12T22:29:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f12fb4d819956cb467b22183f0416fed44703d0f'/>
<id>urn:sha1:f12fb4d819956cb467b22183f0416fed44703d0f</id>
<content type='text'>
Until we did PKCS#7 unwrapping, no leaf MIME part could have a child.

Now, we treat the unwrapped MIME part as the child of the PKCS#7
SignedData object.  So in that case, we want to show it instead of
deliberately omitting the content.

This fixes the test of the protected subject in
id:smime-onepart-signed@protected-headers.example.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
</feed>
