1783288 - Invalid S/MIME Digital Signatures with certain footer-signatures (involving  )

Status: UNCONFIRMED

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

Description

[MindThe&nbsp]

Steps to reproduce:

Sending messages from Thunderbird with proper/valid S/MIME certificates for signature validation AND simple signature text using HTML that contains <a href="https//:sitename">.

Actual results:

When sending messages composed in HTML format, digital sig is 'valid' in sent folder but Not Valid reading in any other mail client (ex. Sending from Zoho account to a gmail).
When sending messages composed in txt-only format, digital sig is 'valid' in sent folder AND is Valid when read in any other email client (ex. Sending from Zoho account to a gmail).

Expected results:

I read all bugzilla threads AND reddit/shit on this issue (See early ver 91 TB issues). Upgraded to 102.1.0 and tried editing my Signature text.
FINALLY found solution: I had an AmpersandNBSP (&NBSP) at the end of my sig text for spacing (I know, a bit of a css style cheat!!).... and without the AmpersandNBSP the issue was FIXED.
Summary: TB 102.1.0 does something to parse the HTML sig incorrectly after sending so the checksum for reader does not add up (my guess based on Sent folder version showing Valid digital sig.)

Comment 1

[MindThe&nbsp]

Steps to reproduce should read:

Sending messages from Thunderbird with proper/valid S/MIME certificates for signature validation AND simple signature text using HTML that contains <a href="https//:sitename"> and simple Signature text ends with &nbsp .

Comment 2

[Hannes]

Is this planned to be fixed? I am sending invalidly signed emails for a long time now. The problem is unavoidable if you answer to HTML emails containing the elements described in the previous comments.