unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Timothy J Miller <tmiller@mitre.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "42637@debbugs.gnu.org" <42637@debbugs.gnu.org>
Subject: bug#42637: [EXT] Re: bug#42637: 27.0.91; mm-view-pkcs7 doesn't handle S/MIME signed andd encrypted messages
Date: Tue, 4 Aug 2020 15:59:06 +0000	[thread overview]
Message-ID: <3649B346-6778-4B76-8940-B066BF24230A@MITRE.ORG> (raw)
In-Reply-To: <873652mna4.fsf@gnus.org>

Sometimes, but I usually get a block of Base64 text.  I'll capture some samples tonight.

-- T

On 8/4/20, 10:41, "Lars Ingebrigtsen" <larsi@gnus.org> wrote:

    Timothy J Miller <tmiller@mitre.org> writes:

    > AFAICT so far, the problem seems to be Outlook but I can't narrow it
    > down further than that since it seems to span multiple versions and
    > platforms.
    >
    > I'll send you a clear signed, opaque signed, encrypted, and
    > signed+encrypted direct.  I *think* only the signed+encrypted will
    > have an issue.

    Yeah, it looks like it -- with the signed+encrypted I just got a blank
    buffer after decrypting.  Is that what you're also seeing?

    > Alternatively, are you aware of this:
    >
    > https://tools.ietf.org/html/rfc4134
    >
    > This test suite would be useful at your end, I should think.  Passing
    > this suite won't eliminate all the bugs b/c every MUA has ... issues
    > regarding S/MIME standards compliance, but it's a good place to start.

    It would be, yes.

    -- 
    (domestic pets only, the antidote for overdose, milk.)
       bloggy blog: http://lars.ingebrigtsen.no


  reply	other threads:[~2020-08-04 15:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 14:22 bug#42637: 27.0.91; mm-view-pkcs7 doesn't handle S/MIME signed andd encrypted messages Timothy J. Miller
2020-08-02  5:07 ` Lars Ingebrigtsen
     [not found] ` <10756_1596344892_5F264A38_10756_6707_1_87y2mxy6s0.fsf@gnus.org>
2020-08-03 13:22   ` bug#42637: [EXT] " Timothy J. Miller
2020-08-04  8:49     ` Lars Ingebrigtsen
2020-08-04 13:16       ` Timothy J Miller
2020-08-04 15:41         ` Lars Ingebrigtsen
2020-08-04 15:59           ` Timothy J Miller [this message]
2020-08-04 16:11             ` Lars Ingebrigtsen
2020-08-04 20:26               ` Timothy J Miller
2020-08-05  8:50                 ` Lars Ingebrigtsen
2020-08-05 12:25                   ` Timothy J. Miller
2020-08-06  7:48                     ` Lars Ingebrigtsen
2020-08-06 13:14                     ` Lars Ingebrigtsen
2020-08-06 14:05                       ` Timothy J Miller
2020-08-06 14:07                         ` Lars Ingebrigtsen
2020-08-06 14:32                           ` Lars Ingebrigtsen
2020-09-07 13:32                             ` Lars Ingebrigtsen
2020-09-07 14:33                               ` Lars Ingebrigtsen

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=3649B346-6778-4B76-8940-B066BF24230A@MITRE.ORG \
    --to=tmiller@mitre.org \
    --cc=42637@debbugs.gnu.org \
    --cc=larsi@gnus.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://git.savannah.gnu.org/cgit/emacs.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).