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

spki: borrow the public key in spki::from_key #1290

Merged
merged 1 commit into from
Jan 4, 2024

Conversation

baloo
Copy link
Member

@baloo baloo commented Jan 3, 2024

SubjectPublicKeyInfoOwned does not require the ownership of the key.

This is a breaking change.

@baloo baloo added the breaking Change to be merged with next release cycle label Jan 3, 2024
@baloo
Copy link
Member Author

baloo commented Jan 3, 2024

Guess I'll need to break this in two.
Release a minor of spki with the first change, then bring that in x509-cert in a follow up.

@baloo
Copy link
Member Author

baloo commented Jan 3, 2024

I am surprised to see minimal version of x509 work here. I expected it to fail, is this not a breaking change?!

@tarcieri
Copy link
Member

tarcieri commented Jan 3, 2024

Not sure how it would be possible?

@baloo baloo force-pushed the baloo/spki/spki-from_key branch from 9df790c to 43f0929 Compare January 4, 2024 18:47
baloo added a commit to baloo/formats that referenced this pull request Jan 4, 2024
`SubjectPublicKeyInfoOwned` does not require the ownership of the key.

This is a breaking change.
@baloo baloo force-pushed the baloo/spki/spki-from_key branch from 43f0929 to 24ef7f6 Compare January 4, 2024 19:47
@baloo baloo merged commit a40e97b into RustCrypto:master Jan 4, 2024
71 checks passed
@baloo baloo deleted the baloo/spki/spki-from_key branch January 4, 2024 20:37
baloo added a commit to baloo/formats that referenced this pull request Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Change to be merged with next release cycle
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants