Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hash collision with owner name #9

Open
vttale opened this issue Mar 7, 2017 · 1 comment
Open

Hash collision with owner name #9

vttale opened this issue Mar 7, 2017 · 1 comment
Labels

Comments

@vttale
Copy link
Collaborator

vttale commented Mar 7, 2017

We should explicitly state what happens in the event a hash matches an existing owner name.

@fcelda fcelda added the NSEC5 label Jun 17, 2017
@fcelda
Copy link
Owner

fcelda commented Jun 17, 2017

We kind of expect that this won't ever happen. NSEC3 suggest to change the salt that we don't have. If the collision happens in NSEC5, the VRF key has to be replaced and that's not easy because all authoritative servers have to follow.

Maybe it would work if the NSEC bitmaps were combined for colliding names. But it breaks some security properties as a result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants