chunk 7 of CMP contribution to OpenSSL#10620
Conversation
|
@mattcaswell, I created this PR starting from the last version of mpeylo#199. If successfully build I would like to ask you for a review. |
|
The time exceeding travis job is probably not related to us. |
a7518fc to
8444614
Compare
|
moved some file updates between the commits, the final result is the same. |
8444614 to
3c550e0
Compare
|
I've just pushed a new version that completes the cleanup of commits that @Akretsch did 8 hours before. |
|
There is - like after the push before - one strange Travis CI failure, which I cannot reproduce locally: |
145680a to
c90f4c9
Compare
|
For what ever reason, Travis keeps aborting its very last job on this PR at Does anyone understand why? This does not seem CMP related. |
|
It seems to be a frequent and very annoying problem at the moment. Don't know why - but it's definitely not CMP related. |
|
Thanks @mattcaswell and @h-vetinari for your (comforting to me) comments! |
|
Travis failures seem relevant. Also, already needs a rebase! |
mattcaswell
left a comment
There was a problem hiding this comment.
For the record I have already reviewed and provided extensive comments on the preview version of this PR.
I've just taken another pass through and just have a few minor comments.
c90f4c9 to
cb5fade
Compare
|
@mattcaswell I fixed the Travis failure and did a rebase. |
31e679e to
ef36932
Compare
@Akretsch, when adding fixes to this PR please always use |
e3f210f to
12b8616
Compare
ce0192a to
49a8b5e
Compare
|
Thanks a lot @bernd-edlinger for very swiftly finishing your review So looks like I can squash and merge this chunk after the usual one day grace period? |
Looks like it - assuming no last minute problems from the CIs. |
|
AppVeyor is always pretty slow, and this time it took even some 12 hours to complete (after presumably being busy grinding on other PRs), but finally it confirmed that the builds and tests pass. |
|
I'll squash the commits (up to a few ones) already now in preparation of the later merge, |
f431d68 to
1b738b3
Compare
1b738b3 to
437d3f0
Compare
|
Done squashing as far as appropriate (and already adding the reviewer & pr info). |
|
We do usually the final squash and rebase without pushing that to the PR again, |
Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Bernd Edlinger <[email protected]> (Merged from openssl#10620)
in particular: consolidate documentation of CMP logging and error reporting functions fix compilation problem with clang on some platforms rename OSSL_CMP_log etc. to ossl_cmp_log etc. since these macros are CMP-internal move chopping of trailing separator to ossl_cmp_add_error_txt(), also fix handling of leading separator internalize X509_print_ex_brief() as x509_print_ex_brief() Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Bernd Edlinger <[email protected]> (Merged from openssl#10620)
…he new util/check-format.pl in addition: correct wording in doc, comments, and parameter names: self-signed -> self-issued where appropriate Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Bernd Edlinger <[email protected]> (Merged from openssl#10620)
add CMP message validation and related tests; while doing so:
* add ERR_add_error_mem_bio() to crypto/err/err_prn.c
* move ossl_cmp_add_error_txt() as ERR_add_error_txt() to crypto/err/err_prn.c
* add X509_STORE_CTX_print_verify_cb() to crypto/x509/t_x509.c,
adding internally x509_print_ex_brief(), print_certs(), and print_store_certs()
* move {ossl_cmp_,}X509_STORE_get1_certs() to crypto/x509/x509_lu.c
Reviewed-by: Matt Caswell <[email protected]>
Reviewed-by: Bernd Edlinger <[email protected]>
(Merged from openssl#10620)
437d3f0 to
31b28ad
Compare
Yes, but @mattcaswell recently asked me regarding PR #10667 to squash it before it was merged, and this had the nice effect that GitHub has been able to recognize the merge automatically, which is indicated by the purple 'Merged' label. I appreciate this, and others as well, and @beldmit even asked to 'incorporate the brilliant changes he made to the workflow' - see #11038
Good to know, thanks @bernd-edlinger.
Yes, this indeed is a drawback. One could still follow up the commits via the link you gave and via its parent link etc, but this would be pretty cumbersome.
Before force-pushing I double-checked this using |
|
@Akretsch, if you still have the previous state of |
|
cmpossl_incremental7-orig pushed |
|
yes, that would be nice, |
|
@bernd-edlinger, good idea to reset to the commit in question first. |
levitte
left a comment
There was a problem hiding this comment.
I just noticed these two put_error calls, which suggest that ERR_add_error_txt() isn't as generic as the function name suggests and possibly should have stayed in the CMP subsystem...
|
@DDvO Have the CMP feature and CRMF feature been completed? Are the test cases completed? When are these features planned for openssl 3.0.0? |
|
@yangyangtiantianlonglong, the state of the CMP contribution is shown and kept up-to-date at https://github.com/mpeylo/cmpossl/wiki#planning-and-current-status-of-the-contribution-chunks. |
Looks like you had an inconsistent source tree or build. |
Certificate Management Protocol (CMP, RFC 4210) extension to OpenSSL
Also includes CRMF (RFC 4211) and HTTP transfer (RFC 6712)
CMP and CRMF API is added to libcrypto, and the "cmp" app to the openssl CLI.
Adds extensive man pages and tests. Integration into build scripts.
7th chunk: CMP protection verification
in
crypto/cmp/cmp_vfy.cand related files.This PR includes also some improvements in code formatting (triggered by #10363) , logging and internal documentation.
Checklist