Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rfc 6376 compliance #5

Open
timcoote opened this issue Apr 14, 2024 · 0 comments
Open

rfc 6376 compliance #5

timcoote opened this issue Apr 14, 2024 · 0 comments

Comments

@timcoote
Copy link

Thanks for this, one of the best explanations of the details of dkim that I've found - and useful as there are some odd dkim signature fails.

One thing that I'm not clear on. Line 219 of README.md, in a section on relaxed header canonicalization:
- remove duplicate entrys (like the to:to:), and the supporting code in hash_headers:
header_to_hash_list.remove(header) # strip duplicate header like the from

seem to me to be in contradiction with the rfc, which says in section 3.5, in the section discussing the h= tag in the DKIM-Signature header field:
"The field MAY contain multiple instances of a header
field name, meaning multiple occurrences of the corresponding
header field are included in the header hash. "

And if the duplication is allowed, the signature does fail.

Is this a bug in the example (+ the system that signed the example email), or have I got something wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant