![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
alexpgpAs a test of the signing capability of the Enigmail addon to Thunderbird, I copied a recipe that was in an open text file, pasted it into an email, signed the thing, and sent it to my Gmail account. Then I sent it right back, and the signature was rejected.
Puzzled, I looked at the messages for some obvious clue. There was none.
Then I saved each message and looked at them inside a binary editor. Bingo!
A tab character in the outgoing message had been converted into a series of seven space characters in the incoming message, which explained the rejection problem. Changing a single character inside of a signed message will cause the signature verification to fail.
I sent another message, making sure there were no tabs in it. And I sent it right back to myself.
Surprisingly, it failed, too, owing to some "quoted printable characters" in the armor, according to the error message. This I shall have to investigate later, when I have some time.
I sent a third message, this time with no tabs or accented characters. Same drill.
Success!
One learns something new every day. Now, back to work!
Cheers...
UPDATE: On a hunch, I changed the default in/out character sets to UTF-8 and repeated the second test. Success!
Puzzled, I looked at the messages for some obvious clue. There was none.
Then I saved each message and looked at them inside a binary editor. Bingo!
A tab character in the outgoing message had been converted into a series of seven space characters in the incoming message, which explained the rejection problem. Changing a single character inside of a signed message will cause the signature verification to fail.
I sent another message, making sure there were no tabs in it. And I sent it right back to myself.
Surprisingly, it failed, too, owing to some "quoted printable characters" in the armor, according to the error message. This I shall have to investigate later, when I have some time.
I sent a third message, this time with no tabs or accented characters. Same drill.
Success!
One learns something new every day. Now, back to work!
Cheers...
UPDATE: On a hunch, I changed the default in/out character sets to UTF-8 and repeated the second test. Success!
