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

Detect and warn about possibly spoofed mail headers #102

Closed
lieser opened this issue Apr 1, 2018 · 4 comments
Closed

Detect and warn about possibly spoofed mail headers #102

lieser opened this issue Apr 1, 2018 · 4 comments
Assignees
Milestone

Comments

@lieser
Copy link
Owner

lieser commented Apr 1, 2018

Try to detect possibly spoofed mail headers, there TB is not showing/using the signed header but one that was added after the signature. If this is detected, either add a waring or let the verification fail.

See http://noxxi.de/research/breaking-dkim-on-purpose-and-by-chance.html#hdr2 for some examples.

Maybe also warn if critical headers (e.g. from address) are not signed.

@ale5000-git
Copy link

Does having multiple subject lines in mails make sense?
If not I suggest to fail completely when it is detected (not just warn).

@lieser
Copy link
Owner Author

lieser commented Sep 18, 2019

I don't know of a valid reason for multiple subject lines, and seems to be even a violation of the e-mail RFC (https://tools.ietf.org/html/rfc5322#page-21). Same for multiple From headers.

What will be a hard failure, or what a waring exactly is not yet decided. And probably also will not be before I look into this in detail than it gets implemented.

But at least for multiple subjects/from headers, I currently don't see a reason why it should be anything less than a hard failure, like you also suggest.

@lieser
Copy link
Owner Author

lieser commented Jun 19, 2022

Added a heuristic to detect this. Simply checks that if one the the headers the RFC recommends or advices to sign is present and signed at least once, that all present headers of that type are signed.
That should be able to prevent many of this attacks of added headers.

@lieser lieser closed this as completed Jun 19, 2022
@lieser
Copy link
Owner Author

lieser commented Jun 19, 2022

Forgot to mention, a version to try this out can be downloaded from #277 (comment).

@lieser lieser self-assigned this Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants