-
Notifications
You must be signed in to change notification settings - Fork 7
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
omit OneAsymmetricKey.publicKey field #65
Conversation
the raw octet string encoding of the 64-octet seed. | ||
the raw octet string encoding of the 64-octet seed. The publicKey field | ||
SHOULD be omitted because the public key can be compute as noted earlier | ||
in this section. | ||
|
||
<aside markdown="block"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, now that the public key friend is recommended to be omitted, this NOTE isn't needed anymore.
@@ -279,7 +279,9 @@ algorithm itself. | |||
</aside> | |||
|
|||
When used in a OneAsymmetricKey type, the privateKey OCTET STRING contains | |||
the raw octet string encoding of the 64-octet seed. | |||
the raw octet string encoding of the 64-octet seed. The publicKey field | |||
SHOULD be omitted because the public key can be compute as noted earlier |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: "computed". I'd phrase it like "because the public key is computed as part of using the private key".
Closes #60.