[GH-ISSUE #87] Does simple/simple (normalizing) break S/MIME? #68

Closed
opened 2026-02-26 10:35:35 +03:00 by kerem · 2 comments
Owner

Originally created by @Pro on GitHub (May 8, 2015).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/87

If canonicalization simple is used, it may break an already existing S/MIME signature because the body is changed (i.e. line endings and header names are normalized according to the DKIM RFC)

This needs further investigation. See also #86

Originally created by @Pro on GitHub (May 8, 2015). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/87 If canonicalization `simple` is used, it may break an already existing S/MIME signature because the body is changed (i.e. line endings and header names are normalized according to the DKIM RFC) This needs further investigation. See also #86
kerem 2026-02-26 10:35:35 +03:00
Author
Owner

@AlexLaroche commented on GitHub (May 8, 2015):

@Pro : If canonicalization simple is active, we calculate the dkim signature on the original email. If canonicalization relaxed is active, we normalize a copy of the email to calculate the email. We aren't supposed to change the original email. The only thing the signer is suppose to do is to add the calculated DKIM signature.

<!-- gh-comment-id:100357621 --> @AlexLaroche commented on GitHub (May 8, 2015): @Pro : If canonicalization simple is active, we calculate the dkim signature on the original email. If canonicalization relaxed is active, we normalize a copy of the email to calculate the email. We aren't supposed to change the original email. The only thing the signer is suppose to do is to add the calculated DKIM signature.
Author
Owner

@Pro commented on GitHub (May 8, 2015):

Oh right, I mixed simple and relaxed up.
But I wasn't sure if if S/MIME also includes headers into the signature. Looked that up now and also the tests from Bug #86 confirm that we should be fine.

<!-- gh-comment-id:100380960 --> @Pro commented on GitHub (May 8, 2015): Oh right, I mixed simple and relaxed up. But I wasn't sure if if S/MIME also includes headers into the signature. Looked that up now and also the tests from Bug #86 confirm that we should be fine.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dkim-exchange-Pro#68
No description provided.