3 ms·
I’ll have to consider this in my own implementation. That is a reasonable way to detect invalid records. Thanks for the correction. I will add, though, that as
by bluejekyll 7y ago
I’ll have to consider this in my own implementation. That is a reasonable way to detect invalid records. Thanks for the correction.
I will add, though, that as you walk the tree back to the roots, downgrades in the key strength do happen as you get to the root 1024bit keys, which is unfortunate.
Aside from that, if DNSSEC is detected to be blocked, or invalid, there’s currently not great mechanisms of signaling this to end users (in most software) to either opt into the security risk or notify them, beyond just failing the lookup.
- deleted 7y ago[deleted]
- teddyh 7y ago> the root 1024bit keys I was under the impression that the root key is now 2048 bits, since October 2018, over a year ago. > there’s currently not great mechanisms of signaling this to end users Not unlike SMTP, but we seem to have managed to transition to mostly TLS-encrypted mail transport.