Add support for requesting Certificate Transparency to clients#1
Open
aeijdenberg wants to merge 22 commits into
Open
Add support for requesting Certificate Transparency to clients#1aeijdenberg wants to merge 22 commits into
aeijdenberg wants to merge 22 commits into
Conversation
Wrap it for C++ like other headers.
I fuzzed this with AFL for a day and found no crashes.
Some flapping "make depend" churn.
…ormats, and basics for validating.
clang suggests %llu instead, but it isn't clear that is portable on all platforms. C99 and above define a handy macro for us, so we try to use that definition and fall back to current definition if needed (though we switch to 'u' for unsigned).
Without this fix "openssl ocsp -port xxx" will cause "openssl s_server -status" calls to hang on FreeBSD. I'm not 100% sure this is the right overall fix... my knowledge here is weak, but it is verified to fix the problem I was having.
aeijdenberg
force-pushed
the
ct-on-steve-sct
branch
from
50cc3e0 to
2064502
Compare
ekasper
pushed a commit
that referenced
this pull request
Nov 8, 2016
PKCS #1 v2.0 is the name of a document which specifies an algorithm RSASSA-PKCS1-v1_5, often referred to as "PKCS #1 v1.5" after an earlier document which specified it. This gets further confusing because the document PKCS #1 v2.1 specifies two signature algorithms, RSASSA-PKCS1-v1_5 and RSASSA-PSS. RSA_sign implements RSASSA-PKCS1-v1_5. Refer to the document using the RFC number which is easier to find anyway, and refer to the algorithm by its name. Reviewed-by: Kurt Roeckx <kurt@roeckx.be> Reviewed-by: Rich Salz <rsalz@openssl.org> GH: openssl#1474
ekasper
pushed a commit
that referenced
this pull request
Jan 25, 2017
PKCS #1 v2.0 is the name of a document which specifies an algorithm RSASSA-PKCS1-v1_5, often referred to as "PKCS #1 v1.5" after an earlier document which specified it. This gets further confusing because the document PKCS #1 v2.1 specifies two signature algorithms, RSASSA-PKCS1-v1_5 and RSASSA-PSS. RSA_sign implements RSASSA-PKCS1-v1_5. Refer to the document using the RFC number which is easier to find anyway, and refer to the algorithm by its name. Reviewed-by: Kurt Roeckx <kurt@roeckx.be> Reviewed-by: Rich Salz <rsalz@openssl.org> GH: openssl#1474 (cherry picked from commit aa90ca1)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merged changes from add_get_peer_scts branch and refactored to use existing SCT primitives with minimal changes to existing functions: