Closed
Bug 202000
Opened 22 years ago
Closed 20 years ago
Incorrect processing of user attached PKCS#7 - files do not display
Categories
(MailNews Core :: Security: S/MIME, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: arnaldo, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401
User creates a PKCS#7 file using a digital signature program. The resulting
PKCS#7 (.p7m) is sent to another using, as an email attachment. On the
destination system, if the mail client is Mozilla (including latest 1.4a) or
netscape, then the attachment will NOT display.
This happens when the p7m file is an attachment (part of a multipart/mixed) and
even when it's the whole thing (the contents of the mail itself is a sole
p7m file - the mail Content-type is set to application/pkcs7-smime).
In either case, the body is a p7m or the p7m being part of a mulitpart body,
the MUA must allow access to it, specially when the PKCS#7 contains data.
Sounds like Mozilla is handling all PKCS#7 as detached signatures.
Reproducible: Always
Steps to Reproduce:
1. Use some application to create PKCS#7 file, containing data and signature
2. Send mail, attach file created in step (1)
3. Attachment will not display of allow being detached.
Actual Results:
No access to the attached file, unless the user can and knowns how to manually
recover it from the mail storage.
Expected Results:
Process the pkcs#7 file accordingly:
a) If it's detached signature, part of an SMIME multipart/smime file, it working
correctly.
b) If the PKCS#7 contains both the signature and the signed-data, then either
process it correclty (like comming from an SMIME) of let it be an attachment
that Mozilla cannot process.
Summary: Incorrect processing of user attached PKCS#7 - files do not display → Incorrect processing of user attached PKCS#7 - files do not display
Comment 3•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•