Re: Does NSD support ED25519 KSK/ZSK keys?
Wouter Wijngaards <[email protected]>
| Newsgroups | gmane.network.dns.nsd.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Vladimir, Yes, NSD supports that. Because NSD is designed to copy the data to the client, the signatures and the DNSKEY data can be sent straight away. The support itself consists of code to parse identifiers used when reading the zone file. If that concluded successfully, then the further operations should be unproblematic. ldns-keygen and ldns-signzone have been updated in the code repository with the new algorithms. Best regards, Wouter On 26/03/2019 05:21, Vladimir Lomov wrote: > Hello, > > the current ldns-keygen/ldns-signzone doesn't support ED25519/ED448 > KSK/ZSK keys while dnssec-keygen can generate ED25519 keys. I generated > ED25519 KSK and ZSK keys using dnssec-keygen, published them in zone > file, checked the zone file (it is Ok) and sign zone by dnssec-signzone. > Though NSD was restarted successfully I wonder (actually I concern) does > NSD works fine with such keys? > > I'm asking because I faced with strange problem with one of Registrar > (name.com) which supports ED25519/ED448 keys but their web interface > being able retrieve DNSKEY record from my DNS server unable to register > on their side the DS record for my DNS server. > > Could it be that NSD couldn't work with ED25519 and sending wrong data > to Registrar when it tries to form DS record? > > --- > WBR, Vladimir Lomov > > > _______________________________________________ > nsd-users mailing list > [email protected] > https://open.nlnetlabs.nl/mailman/listinfo/nsd-users _______________________________________________ nsd-users mailing list [email protected] https://open.nlnetlabs.nl/mailman/listinfo/nsd-users
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE7fqj8spObrBWga+On28cLX4EX40FAlyZzS8ACgkQn28cLX4E X40USA//abJDHFScA+S3aIp1K6wnhUzbI6cHjDvo2g+LkfcjpWsHpKSZI2zGLsfl jfrsb+iNU6NZCcwdsavACXUgxQKMWYqIunemtdykGyaesxuo4j3C6fKzTURm2V6v /INPEq/xYKim7rj2UwUKSi9njrGS5uxIjCJnPFocqe96b2DcXEITdskU4eKJ19w/ IC5F2KxqfRnULu1oGEEBMp/PGXr1hVu8S+1Q2Z2UagtlQdHcRxWtOnGlkZUNo5WN CAFzHLXCjfHJ/s0/Lf7VBCNC2bzjWcx5tp89N8SHhcNmk6MLGdJWjECanx4H460D 1qRVAS1BfRpBRhIcxRCIvw3wn5gUJdTfCi2DNvtoEQyL+e5kpA7kQQxfY81fWpr9 /t+2+rbQdUDZDpxR5nUbGVnq2FbwJDPBGjnQbWP/5Z12VYvmroC7W42dTmXMz6fe L6EQJ+9ZU7k7t6YtPNjJJo0vm7bkeqDm4Pxvw7gRFeUX3/2lq4D6uHsoIQPYT13Y CV1jJU3Wx+W/1F/aB5PLWouYKZEy6wzZwk9DbqcX8bK8EeNcDpV2bJOCGCm/4FGO jMHoJmmrDLZPfnZcObdELD/MibeswUZivRsqOdJUI0IVrbPA/DvlznKVPauJIgde hl+sY4vA9VRq7V+YbVG2jUv4dqLu4hfCSte7pK+oMeM4Mwwgp1I= =n/CK -----END PGP SIGNATURE-----