On 31/05/06, Markku Uttula <[EMAIL PROTECTED]> wrote:
Umm... the BOM is in the message source, which is what should be checked; not the output.
True, this is probably one of the anomalies of clear signing, but ultimately, the question is whether the BOM should be there in the first place. It wouldn't be a problem if mail clients/text editors displyed it, but they correctly remove it.
If this were the case, for example HTML-messages would be unable to be signed since the output doesn't match the input.
HTML and other non 'text/plain' messages cannot be clear signed, they are wrapped in a PGP Mime envelope.
After all, the signing has been done with the encoded version (including possible BASE64/Quoted Unreadable encoding) and if such things are stripped (as they are in the output), the signatures don't match - never.
Yes, for text there is 8 Bit encoding which works fine (no modifications to text), other encoding schemes do not work in this situation. ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
