2 ms·
You missed that servers processing email routinely add or adjust headers. And some servers add trailing content. DKIM was designed to work with email as it exi
by toast0 3y ago
You missed that servers processing email routinely add or adjust headers. And some servers add trailing content.
DKIM was designed to work with email as it exists, so the signer can pick which headers to include in the signature. And l= was included to allow for mailing list servers and other things to add trailers without breaking signatures or needing to sign again.
- magicalhippo 3y agoBut does the recipient need to trust those headers? Couldn't it just remove those non-signed headers before decoding. If not, what does it really buy you? Slight fuzzy feeling? In the article they describe an attacker changing Content-Type as it's typically not signed. That seems like exactly the kind of header you'd want to ignore if not signed.
- Avamander 3y ago> In the article they describe an attacker changing Content-Type as it's typically not signed. That seems like exactly the kind of header you'd want to ignore if not signed. That would result in a lot of unreadable emails unfortunately. It would also take over-signing the Content-Type to mitigate this issue, having everything signed that way would certainly break even more.
- deleted 3y ago[deleted]