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

omit OneAsymmetricKey.publicKey field #65

Merged
merged 3 commits into from
Oct 23, 2024
Merged

Conversation

seanturner
Copy link
Collaborator

Closes #60.

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">
Copy link
Contributor

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
Copy link
Collaborator

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".

Now that we are SHOULD omit publicKey, we don't need the note anymore.
@seanturner seanturner merged commit bd602ca into main Oct 23, 2024
2 checks passed
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 this pull request may close these issues.

Disallow public key in private key
3 participants