Closed
Bug 179082
Opened 22 years ago
Closed 22 years ago
Forward inline an encrypted message base64-encodes attachments twice
Categories
(MailNews Core :: Security: S/MIME, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.3alpha
People
(Reporter: KaiE, Assigned: bugzilla)
References
Details
Attachments
(1 file)
572 bytes,
patch
|
KaiE
:
review+
sspitzer
:
superreview+
|
Details | Diff | Splinter Review |
Prepare your environemnt for S/Mime encryption. Compose a new message and choose to encrypt it (but not sign it, for simplicity). Attach a binary file to the message, like an image. Send the message to yourself. Receive the message. Choose to forward inline. Turn off encryption and signing. Send the message to yourself. Receive the message. Expected behaviour: The attachments should display correctly. Actual behaviour: The attachments are broken. I looked into this a bit more already. What actually happens is that the incoming message contains the attachments, but they were base64 encoded twice. If I manually access the message source, and copy an attachment to a file, and can get to the file by running base64-decode tools twice on it. The intention of this bug is that we prevent encoding base64 twice when not necessary.
Reporter | ||
Comment 1•22 years ago
|
||
Note that this bug is unrelated to the upcoming fix to bug 161488. The behaviour is the same, regardless whether you use the fix for bug 161488 or not.
Assignee | ||
Comment 2•22 years ago
|
||
Does signing the forwarded message is a requirement?
Reporter | ||
Comment 3•22 years ago
|
||
It does not matter whether you sign or not, and it does not matter whether you encrypt or not. If the initial message was encrypted, had attachments, and you forward inline, all four combinations - not sign, not encrypt - sign, not encrypt - not sign, encrypt - sign, encrypt produce the incorrect message as described in this bug.
Assignee | ||
Comment 4•22 years ago
|
||
The image extracted from the original message and saved in the temp directory is not decoded for some reason! Something wrong in mimedrft.cpp...
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•22 years ago
|
||
the problem is caused by the line http://lxr.mozilla.org/seamonkey/source/mailnews/mime/src/mimedrft.cpp#1968 mdd->options->decrypt_p is true therefore we by-pass the decoding! I need to figure out why we do that test...
Assignee | ||
Comment 6•22 years ago
|
||
reassign to myself
Assignee: kaie → ducarroz
Status: ASSIGNED → NEW
Whiteboard: have fix
Assignee | ||
Comment 7•22 years ago
|
||
This line of code comes from 4.x. Things were little bit different at that time. I could not find any good reason to haveit anymore in MOzilla! I remove the test of decrypt_p and everything works well now. I tested a lot of scenario and cannot find any problem.
Assignee | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → 1.3
Reporter | ||
Comment 8•22 years ago
|
||
Comment on attachment 105873 [details] [diff] [review] Proposed fix, v1 This patch works fine for me. r=kaie
Attachment #105873 -
Flags: review+
Comment 9•22 years ago
|
||
Comment on attachment 105873 [details] [diff] [review] Proposed fix, v1 sr=sspitzer
Attachment #105873 -
Flags: superreview+
Assignee | ||
Comment 10•22 years ago
|
||
Fixed in the trunk
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 11•22 years ago
|
||
20021203 Trunk Build. Verified on Linux, Win2k. Could not verify on OSX as I reopened bug 156958.
Reporter | ||
Comment 13•22 years ago
|
||
*** Bug 190096 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•