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

Private key storage #8

Open
vttale opened this issue Mar 7, 2017 · 4 comments
Open

Private key storage #8

vttale opened this issue Mar 7, 2017 · 4 comments
Labels

Comments

@vttale
Copy link
Collaborator

vttale commented Mar 7, 2017

Section 12.2:

" This document does not define a format to store private NSEC5 keys.
Use of a standardized and adopted format is RECOMMENDED."

This feels awfully squishy to me. It should either just declare the whole issue out of scope and drop the second sentence, or recommend something more concrete. As an implementor reading it I simultaneously react with both "well yes of course, that makes obvious sense" and "which?".

@goldbe
Copy link
Collaborator

goldbe commented Mar 9, 2017

looks like someone made this change already so i am closing this issue.

@goldbe goldbe closed this as completed Mar 9, 2017
@vttale
Copy link
Collaborator Author

vttale commented Mar 10, 2017

Actually that's what it says now. I'm suggesting it be changed.

@vttale vttale reopened this Mar 10, 2017
@goldbe
Copy link
Collaborator

goldbe commented Mar 10, 2017

cool. change it then :)

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

fcelda commented Jun 17, 2017

This was added because there were questions from the community how the key will look like. But I don't want to standardise anything about the key format and its distribution. I would leave this up to the implementers.

So do you wanna drop this part?

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

3 participants