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

bns-prove: support PKCS 11 for HSM signing #29

Open
pinheadmz opened this issue Apr 15, 2021 · 0 comments · May be fixed by #30
Open

bns-prove: support PKCS 11 for HSM signing #29

pinheadmz opened this issue Apr 15, 2021 · 0 comments · May be fixed by #30

Comments

@pinheadmz
Copy link
Collaborator

ICANN TLD owners can claim their names on Handshake following the reserved name-claim process. However, TXT records are prohibited in the apex of a TLD zone, so those users will have to use the bns-prove tool to create the DNSSEC proof outside the legacy DNS. The tool currently requires direct access to the ZSK and KSK:

From https://hsd-dev.org/guides/claims.html:

The private keys themselves must be stored in BIND’s private key format (v1.3) and naming convention.

This poses a problem to TLD owners who use secure hardware to sign DNSSEC messages.

One solution could be adding two additional functions to bns-prove:

  1. Format the claim TXT record in such a way that HSMs can sign it. This may be unnecessary since the HSM operator likely already has a process in place for signing DNS records with the machine. Formatting the TXT signing request with PKCS11 may refine this process.

  2. Combine the signed TXT as returned by the HSM into the root of the DNSSEC proof so the Handshake claim transaction can be completed and submitted to the network.

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

Successfully merging a pull request may close this issue.

1 participant