S/MIME encryption mangles special characters
-
Volker Kopetzky
Seems to be fixed now, I'll try to document this for the internet eternal.
- Generate usual S/MIME stuff
- private key
- certificate (cert-A)
- e.g. startssl
- Import to os x key chain
- exchange signatures with addressee
- Send emails with nice umlauts
- Setup a scond computer (and forget to copy your
certificates)
- regenerate certificate with the same key
cert-B has the same signature as cert-A but different hashes/fingerprint and expiration date than the initial one - send email with cert-B
- receiver gets scrambled umlauts
- ask receiver to import your new cert/signature again
- receiver sees nice umlauts again
Sender: MailMate/mac
Receiver: Outlook/WinKinda makes no sense, does it?
- Generate usual S/MIME stuff
-
benny
- State changed from new to cantreproduce
What you see as mangling is the so-called quoted-printable encoding. This is used to convert message content to 7 bit (for historic reasons). The problem is unlikely to be related to keys/certificates. It is more likely to be some kind of issue (sender or recipient) which makes decoding the message fail.
If you get MailMate back into this state (in that case, try sending a message to me via “Help ▸ Send Feedback” such that I can see the issue myself).
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.