(This bug imported from BugSplat, Netscape's internal bugsystem. It was known there as bug #83700 http://scopus.netscape.com/bugsplat/show_bug.cgi?id=83700 Imported into Bugzilla on 04/26/00 15:31) Seen on 8/27 SunOS build and on PC Win32 4.02: Create a new message, signed and encrypted, and send it to yourself Forward the message to yourself, sign and encrypt it Reply to the message (should go back to you with previous text quoted), sign and encrypt it View the message Observe the broken security lock icons in the quoted sections where it says "signed and encrypted". Instead of the icon, it has a broken icon and the text "S/MIME". ------- Additional Comments From repka 07/28/98 15:12 ------- *** Bug 301971 has been marked as a duplicate of this bug. *** ------- Additional Comments From repka 07/28/98 15:59 ------- [FYI, you may want to look at the text in bug 301971 for another view on the problem. But I have tried to include all of the necessary information here.] Here is what I think is the minimum needed to reproduce this bug: - Have HTML mail compose turned on. - View a message with an S/MIME *attachment*. (This can be one you already happen to have or one you create. It can be signed or encrypted or both, though just signed is probably the easiest to deal with and to pass around to others. It doesn't matter as long as it is an attachment with a nice S/MIME icon showing in its header. But bug verifiers may want to be thorough and try all combinations.) - Do a quoted reply to that message. The problem is that the quoted HTML includes the S/MIME icon/link, but it shouldn't. Note that if you take the same message and do a quoted forward on it, the quoted HTML does not include the S/MIME icon/link. I think that if the quoted forward is able to avoid including the S/MIME icon/link, there is probably (hopefully?) a way to make the quoted reply do it similarly, too. Also note that if you are replying using plain text, not HTML, you get a textual representation of the S/MIME icon/link. That shouldn't be there either, but I think it will fall out in the wash when the HTML problem is fixed, because that textual representation also does not show up in the quoted forward. I'm not sure if this problem is in libmime, or in the invocation of it, but given the quoted forward behavior, I'm presuming the latter. Jamie may be able to shed a little light on that, if he is so inclined. In any case, I don't think this is my bug at all, so I'm starting with jefft as my best guess. Jeff, please reassign as appropriate. ------- Additional Comments From jefft 07/30/98 13:59 ------- Looks like this has been fixed in Nova. Forward Qutoed & Reply Quoted do not include attachment's S/MIME icon. However, Forward As Attachment does include the S/MIME icon. ------- Additional Comments From repka 07/30/98 14:07 ------- > However, Forward As Attachment does include the S/MIME icon. Forwarding the message itself (as opposed to quoting it) doesn't include the icon but rather the entire message, which then gets decoded and interpreted by the recipient, who does their own signature verification. It is very different (and fine) behavior. The (apparently now fixed) problem was that when quoting, only the text gets taken (and the signature, for example, gets thrown away) but that icon tossed in there was inappropriate. Anyway, glad to hear the bug is gone. ------- Additional Comments From repka 07/30/98 14:18 ------- Sorry, one more question: > Looks like this has been fixed in Nova. This bug was reported against Nova very recently (bug 301971, which I closed as a dup of this one). Bob Lord was able to reproduce it with a fairly current Nova. Do you know how/why the bug went away? I think the change must have been made within the last week or two, given that lord saw it on 7/24 (not sure what build he was running). I'd like to understand how this stuff works, why it behaved the way it did, etc., if it doesn't take too much of your time. ------- Additional Comments From lord 07/30/98 16:53 ------- I just downloaded today's version of Nova, and it is not fixed. It's trival to reproduce based on the script davidi provided. There may have been other fixes recently, but this one is still broken. ------- Additional Comments From jefft 07/30/98 18:15 ------- If Forward Quoted or Forward Inline then reply the problem does *not* exist. If Forward as Attachment then reply the problem does exist. Reply quote forward-as-attachment message in html picks up the S/MIME icon. See the following html content from the mail compose window. Looks like we need to find a way to strip out the S/MIME icon while quoting. (Similar thing to do when reply quote into plain text.) I should have tried Forward As Attachment then reply. Sorry... <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML> &nbsp; <P>&nbsp; <P>Jeff Tsai wrote: <BR>&nbsp; <BLOCKQUOTE TYPE=CITE> test forward <BR>&nbsp; <TABLE BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" > <TR VALIGN=TOP> <TD WIDTH="100%"> <HR WIDTH="90%" SIZE=4> <P><NOBR><B>Subject: </B>test</NOBR> <BR><NOBR><B>Date: </B>Thu, 30 Jul 1998 17:52:40 -0700</NOBR> <BR><NOBR><B>From: </B>Jeff Tsai &lt;jefft@netscape.com></NOBR> <BR><NOBR><B>To: </B>jefft@netscape.com</NOBR> <BR>&nbsp;</TD> <TD ALIGN=RIGHT VALIGN=TOP> <CENTER><TABLE BORDER CELLSPACING=0 CELLPADDING=3 > <TR> <TD ALIGN=RIGHT VALIGN=BOTTOM BGCOLOR="#FFFFFF"><A HREF="about:security?advisor=IMAP://nsmail-2?fetch>UID>/INBOX>40 52&part=1.1.1.2" onMouseOver="window.stat<A HREF="about:security?advisor=IMAP://<IMG SRC="internal-smime-signed" ALT="S/MIME" BORDER=0 ></A> <BR><B><FONT COLOR="#FF0000"><FONT SIZE=-1>Signed</FONT></FONT></B></TD> </TR> </TABLE></CENTER> </TD> </TR> </TABLE> <P>test <BR><IMG ISMAP SRC="IMAP://nsmail-2?fetch>UID>/INBOX>4052&part=1.1.1.2.1.1.2" ALT="Netscape Netcenter" BORDER=0 USEMAP="banner<IMHEIGHT=42 WIDTH=579> <BR>&nbsp;</BLOCKQUOTE> </HTML> ------- Additional Comments From jfriend 08/31/98 13:17 ------- Major XP/IMAP Bug triage. TFV set to 4.5Later, resolution set to Later. ------- Additional Comments From jfriend 08/31/98 13:20 ------- Changing TFV 4.5Later bugs to Resolution LATER. ------- Additional Comments From marek Feb-23-2000 17:28 ------- Resolving all 4.5 bugs so far resolved as REMIND and LATER as WONTFIX.

Old bug just moved from internal to bugzilla. Reopening so I can reassign it and comment on it.

Okay, Christian. Here's one more bug that is *not* an NSS bug. But since the 6.0 client doesn't have S/MIME in it anyway, and I don't want the problem to get lost/forgotten, I'm giving it to you. You can deal with it any way you like, including adding to a list of things to test for later and then closing the bug altogether. FYI, the way to test this is to follow the instructions I added on 7/28/98; they are the minimum to cause the problem and thus should be the easiest way to test and debug it. If you follow the original instructions you end up working with encrypted messages, but the encryption wasn't necessary to cause the problem and only results in messages you can't easily pass around.

Confirming again; repka@netscape.com - how come all the bugs you import are starting off as UNCONFIRMED? You seem to have the correct privs. to create NEW ones... Gerv

Oops; actually doing it this time. Gerv

This bug should be considered when S/MIME is integrated into Mozilla.

reassigning to ducarroz

Now that Mozilla support smime, I have tested using both forward as attachment and forward inline and it is working fine for me.

verified wfm