-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <[email protected]>, John Levine
<[email protected]> writes

>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. 
>
>I don't think that's it.  Everyone figured out how to handle RSA signatures,
>and the spec we wrote for Ed25519 was clear enough that nobody I know had
>significant trouble implementing it.

$DAYJOB$ eventually got around to it a couple of years back because up
to then nobody cared. It didn't interwork reliably for headers (bodies
was fine)... it had never been a priority, and complex debugging
certainly was not.

It was recently noticed on the backlog (because of DKIM2 as it happens)
and the code inspected ... the third party library we were using was
updated (many years after it should have been). It now appears we can
validate Ed25519 signatures.

This is a story about retrofitting and the priority people give to that.
It's why, in my view, we need all the algorithms we ever expect to use
before DKIM3 comes along in the RFC the first day it is published.
Changing the list thereafter is never going to work out.

>>> Key rotation in DKIM1 doesn't work in practice, mostly because you have
>>> to have separate selectors for different algorithms which means double
>>> signing, which risks losing mail in badly designed receivers that
>>> penalize signatures they can't verify.  I think we fixed this in DKIM2 ...
>
> ... by allowing multiple signatures in each header.  They have to be ORed
>or algorithm rotation isn't going to work.

Yes, you need to OR the results for the same algorithm

>I don't think an AND option
>makes sense unless you can explain to me what is the correct thing to do
>with a signature with two signatures, one of which you can verify and passes,
>and the other you don't understand at all and can't even try to verify.

as expressed you are in a state of sin for failing to implement required
algorithms (or the Signer is in a state of sin for putting in an
algorithm name that is not in the specification). It's one of the few
MUSTs for a Verifier -- ALL signing algorithms and hash functions MUST
be implemented.

- -- 
richard @ highwayman . com                       "Nothing seems the same
                          Still you never see the change from day to day
                                And no-one notices the customs slip away"

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBatVpBWHfC/FfW545EQLO4QCgg21weJOfjbDEcx+5rmwfCATw4PAAnA7Y
jYi70oH8OCqPc9iU/YATnx/M
=/zvB
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to