On Sun, 18 Oct 2026, Wei Chuang wrote:
It appears that Wei Chuang <[email protected]> said:
... I agree that we shouldn't underestimate the difficulties of
introducing a new algorithm, as we saw with the friction of getting DKIM
operators to adopt Ed25519. I've recently heard one reason was library
compatibility issues.
In retrospect the real reason was obvious: we added Ed25519 as a backup
just in case RSA was broken. Since it wasn't and isn't, there's zero
benefit to Ed25519 so no wonder. I wrote the RFC and even I haven't added
it.
My point is simply that we must respect the effort involved in adding a new
algorithm. My other point is that the draft includes language requiring
the specified algorithms to be mandatory, which raises a concern that this
could become an adoption barrier if we don't consider it carefully.
My impression is that there are about five widely used DKIM
implementations. If they agree to implement the algorithms, we're pretty
much done.
* ORing of multiple signatures - to support buggy implementations with
greater security risk when there is an algorithm vulnerability.
It's to allow algorithm rotation. How else could you do it?
* ANDing of multiple signatures- protection against algorithm vulnerability
but has interop risk
I really would like someone to say what they think is the correct thing to
do when you understand one algo which passes, don't understand the other,
and it says AND. If you pass, that's wrong, but if you don't pass, that's
wrong too.
"If there is more than one signature provided then they MUST all be checked
if the Verifier is able to do so. *If any signature fails then an error
SHOULD be reported*. If all signatures that can be checked fail then FAIL
MUST be reported."
While the ambiguity is intentional, ...
My strong recollection is that "report" meant to log it and report back if
we invent an DKIM2 report scheme, not fail. That situation obviously
means that the signer or verifier is broken (or I suppose maybe both) so
it's a bug report.
R's,
John
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]