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

fixes #4531 -- support encoding SCTs in certificates #5594

Merged
merged 1 commit into from
Dec 1, 2020

Conversation

alex
Copy link
Member

@alex alex commented Nov 30, 2020

No description provided.

@alex alex force-pushed the encode-scts branch 2 times, most recently from a005cec to 4bb8465 Compare November 30, 2020 16:14
@alex alex added this to the Thirty Third Release milestone Nov 30, 2020
@reaperhulk
Copy link
Member

This API only allows encoding of SCTs that were previously parsed by OpenSSL. We have no concrete type for SCT at this time so I understand why it's structured that way, but I think we need a way to create SCTs that doesn't involve just passing through pre-existing pointers.

@alex
Copy link
Member Author

alex commented Nov 30, 2020

You're right that we need that API, but it's a whole separate thing -- we need an SCTBuilder or similar. I'd prefer to defer the implementation of that until we have Rust, since I'll implement it that way (and kill all of our usage of SCT *).

For now, I'd like to finish off the x.509 encode/decode parity.

@reaperhulk reaperhulk merged commit 6d858c8 into pyca:master Dec 1, 2020
@alex alex deleted the encode-scts branch December 1, 2020 03:57
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants