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

In message <[email protected]>, Mauro De
Gennaro <[email protected]> writes

>Some implementation experience that may help before Wednesday's interim:
>
>I have implemented mldsa44-ed25519-sha512 in mail-auth, the Rust library 
>behind 
>Stalwart's DKIM2 support, as part of updating it to draft-ietf-dkim-dkim2-spec-
>07. 

hah, I am reading WG messages in the wrong order, you have beaten Bron's
Claude to it !

>While implementing it I found some points the current texts leave open.

That's charitable, "gets wrong" would be closer

>1. What is signed. Section 3.4 of -07 says the algorithm "computes a hash over 
>all the Message-Instance and DKIM2-Signature fields as described in Section 
>12.8 
>using SHA-512 [FIPS-180-4] as the hash-alg.

I think it's pretty clear we should use either the LAMPs composite
(where the hash is fed into ed25519 and the ML-DSA-44 gets fed the raw
data)

>   I implemented (a), which matches Richard's pointer to the LAMPS draft and 
>avoids hashing twice.

yes I think that's right

>2. Context string. Neither draft specifies an application context, so for the 
>composite the LAMPS default (empty) applies, and that is what I use. Plain ML-
>DSA also takes a context string. Should DKIM2 define one (for example "DKIM2") 
>for domain separation, or is empty deliberate?

empty avoids some bike-shedding, DKIM2 might make some crypto-purists
who worry about cross-protocol attack.

>3. Key encoding. I publish the raw composite public key in p=, that is the 
>1312-byte ML-DSA-44 public key followed by the 32-byte Ed25519 public key, not 
>a 
>SubjectPublicKeyInfo structure, which is how I read dns-01 together with LAMPS 
>Sections 4.1 and 5. Given the RSA format errata in dns-01 Appendix A, it would 
>help to say explicitly whether SPKI is allowed for the new key types.

I think the correct answer here is "we should use whatever off-the-shelf
libraries spit out" (presumably there is some consensus there) ... but
if we don't use a composite scheme then we don't need to decide

>If the interim decides to go with plain ML-DSA-44 instead, adding it on my 
>side 
>is a small change, and I will add it to the playground as well so there is 
>something to interop against.

thank you

- -- 
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/AwUBatY8EWHfC/FfW545EQIesgCfeAViUhpDattCIavnwmpq+hLPJvUAnAlS
k1cY07kubwqNeCy/9qf15oWE
=AVkv
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to