Closed Bug 142115 Opened 22 years ago Closed 22 years ago

w/ S/MIME enabled, emails w/attachments containing either EXE or PDF files display an invalid signature

Categories

(MailNews Core :: Security: S/MIME, defect)

1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 139561

People

(Reporter: trix, Assigned: ssaux)

Details

Description:
Receiving an email with an attachment thats either an EXE or PDF from a sender
with a valid certificate, that email displays a broken signature icon stating
that the certificate from that sender is invalid.

REPRODUCIBLE:
Always

Steps:
1. Install Certificate, enable S/MIME.
2. Send to yourself an email containing an attachment thats either and EXE or PDF.

RESULT:
Displaying that message shows a questionmark signature icon and describes that
this signature is invalid.

NOTE:
Other attachments such as: JPG, GIF, DOC, HTML, XLS, TXT display a valid signature.
changing qa contact to self, since there is relation with attachments. also,
modifying summary 
QA Contact: carosendahl → trix
Summary: w/ S/MIME enabled, an invalid signature is displayed when recieving an email w/attachment → w/ S/MIME enabled, emails w/attachments containing either EXE or PDF files display an invalid signature
Duplicate of bug 139561, which is the result of temporary work performed for
beta in bug 125607.

Note that this size and protocol dependent.  It also reacts differently to
inline vs non-inline attachments.
Nominating.
Keywords: nsbeta1
Also note:  Current behavior is almost identical to that in NS4.79.  The
proposed 'final' fix will allow verification on demand, in addition to the
questionable signature icon/message.
curious to ask - are the DOC and XLS files small in size?

*** This bug has been marked as a duplicate of 139561 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm1.01 → 1.0 Branch
Product: Core → MailNews Core
QA Contact: trix → s.mime
You need to log in before you can comment on or make changes to this bug.