Implementation of ED448

[Floris]

Hello,

Google Public DNS has supported Ed25519 per RFC 8080 since 2018, however, support for ED448 (also RFC 8080) still does not seem to be implemented. Is this planned?

https://rootcanary.org/test.html

[Alex Dupuy]

Floris wrote:

Google Public DNS has supported Ed25519 per RFC 8080 since 2018, however, support for ED448 (also RFC 8080) still does not seem to be implemented. Is this planned?

Given that BoringSSL, Google’s fork of OpenSSL, explicitly does not support ED448, it seems like Google doesn't plan to support it.

[Floris]

Furthermore, looking at RFC 8624 section 3.1, it seems that Google's Public DNS is roughly following the recommendations, but not completely. Below I have copied the table from RFC 8624 and highlighted in green which algorithms Google Public DNS has implemented per recommendation. The algorithms in red are not implemented yet and the one in yellow is optional.

   +--------+--------------------+-----------------+-------------------+

   | Number | Mnemonics          | DNSSEC Signing  | DNSSEC Validation |

   +--------+--------------------+-----------------+-------------------+

   | 1      | RSAMD5             | MUST NOT        |  MUST NOT         |

   | 3      | DSA                | MUST NOT        |  MUST NOT         |

   | 5      | RSASHA1            | NOT RECOMMENDED |  MUST             |

   | 6      | DSA-NSEC3-SHA1     | MUST NOT        |  MUST NOT         |

   | 7      | RSASHA1-NSEC3-SHA1 | NOT RECOMMENDED |  MUST             |

   | 8      | RSASHA256          | MUST            |  MUST             |

   | 10     | RSASHA512          | NOT RECOMMENDED |  MUST             |

   | 12     | ECC-GOST           | MUST NOT        |  MAY              |

   | 13     | ECDSAP256SHA256    | MUST            |  MUST             |

   | 14     | ECDSAP384SHA384    | MAY             |  RECOMMENDED      |

   | 15     | ED25519            | RECOMMENDED     |  RECOMMENDED      |

   | 16     | ED448              | MAY             |  RECOMMENDED      |

   +--------+--------------------+-----------------+-------------------+

I want to applaud Google for dropping MD5 support as the first of all big public providers. I have tested Cloudflare's 1.1.1.1, DNSFilter, Cisco Umbrella/OpenDNS, NextDNS, Quad9, NuSEC, SafeDNS and Yandex DNS – they all happily accept MD5. However, it would be perfect of course if DSA is also phased out (and ED448 implemented). Is this on the roadmap?

[Puneet Sood]

We evaluate DNSSEC algorithm support periodically so we will be looking at removing support for algorithms3, 6 in the next few months. The KSK, ZSK tables at https://stats.dnssec-tools.org/ show that there are less than 1000 domains using algorithm 16.

For algorithm 16 (ED448) since we use BoringSSL for crypto, it will be good to file a feature request there: https://bugs.chromium.org/p/boringssl/issues/list.

 

--
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/public-dns-discuss/d6fc7077-84ce-4f40-ae70-695d99400cban%40googlegroups.com.