[Tickets #13661] Re: Can't decrypt signed message stored in encrypted S/MIME message

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13661
------------------------------------------------------------------------------
  Ticket             | 13661
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Can't decrypt signed message stored in encrypted
                     | S/MIME message
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-11-04 03:47) wrote:

> I have a message which is properly encoded

"properly encoded" is very questionable.

First, it's using the long deprecated MIME type.

Second, it does not contain the smime-data parameter.  From RFC 5751 [3.2]:

    Because there are several types of application/pkcs7-mime objects, a
    sending agent SHOULD do as much as possible to help a receiving agent
    know about the contents of the object without forcing the receiving
    agent to decode the ASN.1 for the object.  The Content-Type header
    field of all application/pkcs7-mime objects SHOULD include the
    optional "smime-type" parameter, as described in the following
    sections.

In other words... that is some garbage input.