David von Oheimb

TLS 1.3: add 'integrity-only' cipher suites

3

This WiP PR is for implementing #18343. The code is (so far) by Yiannis Stavrou of Nozomi Networks of 2019/2020, recently rebased by me on the current master. I also...

`X509_STORE_CTX_set_default()`: improve error handling and reporting, also in its use

3

So far, error result of `X509_STORE_CTX_set_default()` was not checked in `pk7_smime.c` and the error code was misleading in in `x509_vfy.c`. This PR also adds error information which purpose name could...

APPS: generalize `load_csr()` and remove obsolete `OBJ_create()`

2

This has been carved out of #16006 and slightly extended. * Move `load_csr_autofmt()` from `apps/cmp.c` to `apps.c` and use it also for other apps * `apps/x509.c:` Remove legacy call to...

By when to provide PRs for inclusion in 3.1?

3

As I plan to submit further PRs for CMPv3 and likely also for some other new features, are there already estimations when feature freeze is going to be?

* add missing CRMF API function `OSSL_CRMF_CERTTEMPLATE_get0_publicKey()` * CRMF: make `create_popo_signature()` check that pubkey and pkey match The latter has a prerequisite: * X509: clean up implementation of `X509{,_REQ}_check_private_key()` and...

* fix crash in `check_transactionID_or_nonce()` on `actual` being `NULL` * correct handling of fallback subject in `OSSL_CMP_CTX_setup_CRM()` and its doc

crypto/x509 and S/MIME: fix purpose inconsistencies, add missing `smime_encrypt`

3

* Fix inconsistent doc vs. implementation for purposes `smine_sign` and `smime_encrypt` * Add missing purpose `smime_encrypt` in `x509_vpm.c`

* `X509_REQ_get_extensions()`: add error queue entry on ill-formed extensions attribute * add missing doc of `X509_REQ_get_extensions()` and `X509_REQ_add_extensions{,_nid}()` On this occasion, improve error checking and reporting and coding style in...

Add a stand-alone "timing_load_creds" program (was PR 15088/16540)

7

Copy of #16540 by @richsalz, plus new fixups.

PKCS#7 and CMS overlap heavily - deprecate (part of) PKCS7

5

As already mentioned in #18915, there is enormous overlap between the implementations of CMS and PKCS#7, which is no wonder because these two standards are basically the same. This causes...