unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] test: initial tests for smime
Date: Sat, 17 Jan 2015 23:29:11 +0100	[thread overview]
Message-ID: <87sif99h3c.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <87twzpt6e8.fsf@servo.finestructure.net>

Jameson Graef Rollins <jrollins@finestructure.net> writes:

> For some reason PATCH 3/4 no longer applies after substituting in this
> patch as PATCH 1/4.

Ah, I guess I need to send the whole series again.

>
> But do we really need to test the message output of openssl?  It seems
> like it's broken, and if it ever gets fixed we'll need to change this
> test.

I think it's not so much broken as "canonical". There is some discussion
in the openssl-smime man page that pointed me to RFC5751
para 3.1.1

   MIME entities of major type "text" MUST have both their line endings
   and character set canonicalized.  The line ending MUST be the pair of
   characters <CR><LF>

> But all we really care about is that openssl is properly verifying the
> message, yes?  Why not just test that and forget about the rest of
> openssl's output?

Maybe it doesn't add too much as long as the message is using the "clear
signed" multipart/signed format. On the other hand there is an opaque
signed format (application/pkcs7-mime with Signeddata) too, where it
would be interesting to check for mangling of the text. Similarly, when
we add a similar test for encryption, I think we do want to check the
content, so we'll have to figure this out at some point.

Cheers,

d

  reply	other threads:[~2015-01-17 22:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 18:38 S/MIME support Jameson Graef Rollins
2012-06-29 18:38 ` [PATCH 1/2] cli: S/MIME verification/decryption support Jameson Graef Rollins
2012-06-29 18:38   ` [PATCH 2/2] debian: Recommend gpgsm for S/MIME support Jameson Graef Rollins
2012-07-09 18:33 ` Bryant, Daniel B.
2012-07-10  7:40   ` Jameson Graef Rollins
2012-08-31 19:50     ` David Bremner
2014-03-17  4:52 ` S/MIME support, rebased Jameson Graef Rollins
2014-03-17  4:52   ` [PATCH 1/2] cli: S/MIME verification/decryption support Jameson Graef Rollins
2014-03-17  4:52     ` [PATCH 2/2] debian: Recommend gpgsm for S/MIME support Jameson Graef Rollins
2014-07-01 10:55     ` [PATCH 1/2] cli: S/MIME verification/decryption support David Bremner
2014-07-06 17:36       ` Jameson Graef Rollins
2014-07-06 18:18         ` David Bremner
2015-01-17 10:51   ` SMIME patches v3, with some tests David Bremner
2015-01-17 10:51     ` [PATCH 1/4] test: initial tests for smime David Bremner
2015-01-17 10:51     ` [PATCH 2/4] cli: S/MIME verification/decryption support David Bremner
2015-01-17 10:51     ` [PATCH 3/4] test: add S/MIME signature verification test for notmuch CLI David Bremner
2015-01-17 10:51     ` [PATCH 4/4] debian: Recommend gpgsm for S/MIME support David Bremner
2015-01-17 20:07     ` SMIME patches v3, with some tests Jameson Graef Rollins
2015-01-17 21:38       ` [PATCH] test: initial tests for smime David Bremner
2015-01-17 21:59         ` Jameson Graef Rollins
2015-01-17 22:29           ` David Bremner [this message]
2015-01-17 22:54             ` Jameson Graef Rollins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sif99h3c.fsf@maritornes.cs.unb.ca \
    --to=david@tethera.net \
    --cc=jrollins@finestructure.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).