[openssl-dev] [openssl.org #4041] [PATCH] Add Certificate Transparency Support
Adam Eijdenberg
eijdenberg at google.com
Mon Sep 14 18:45:34 UTC 2015
On Mon, Sep 14, 2015 at 11:29 AM Viktor Dukhovni <openssl-users at dukhovni.org>
wrote:
> Is there a document that describes the new functionality? All I
> see is new code, and it is fairly light on comments.
>
> Splitting it up into multiple patches is good, but adoption of a
> new feature really should require that all the patches be available
> together, so that the overall design can be assessed as well the
> individual components.
>
Hi Viktor,
Thanks for the feedback. This branch:
https://github.com/aeijdenberg/openssl/tree/ct-on-steve-sct
has a longer plausible series of commits. The PR submitted in this ticket
helps form the base of that series.
A README describing the proposed end state is here:
https://github.com/aeijdenberg/openssl/blob/ct-on-steve-sct/crypto/ct/README.md
I suspect the final public API surface will generate substantial
discussion, however it felt like there is a good amount of plumbing we need
to get in place first that is likely less interesting / controversial.
Emilia suggested breaking the basics down into some initial PRs, so that's
how I got here. I'm happy to resubmit the patches in any format/structure
that the team finds best to work with.
Cheers, Adam
> So better would be a pull request with multiple commits, rather
> than separate pull requests for each one. It seems unlikely that
> we'll adopt just a subset of the functionality.
>
> --
> Viktor.
> _______________________________________________
> openssl-dev mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20150914/f2224154/attachment-0001.html>
More information about the openssl-dev
mailing list