Monthly Status Report (May 2022)
My key activities this month were: - triage of newly reported issues, investigating bugs, and responding to questions - participation on the meetings - Youtrack workflow experimentation and proposal - participation on QUIC design and implementation - preparation of Technical Policies changes proposals - reviews of various PRs: - I've reviewed more than 80 PRs this month - Notable PRs reviewed: - X509{,_LOOKUP}: Improve distinction between not found and fatal/internal error #14417 - Make configuration (and therefore builds) leaner #16378 - Clear method store / query cache confusion #18151 - tls: ban SSL3, TLS1, TLS1.1 and DTLS1.0 at security level one and above #18236 - Non-locale dependent OPENSSL_strcasecmp #18344 - QUIC wire format support #18382 - http_client.c: trace HTTP requests and responses when enabled #18386 - submitted 15 PRs: - In particular: - Fix build on OPENSSL_SYS_TANDEM and older POSIXes #18241 - Add design requirements for QUIC packet demuxer #18249 - Add a testcase for OSSL_PROVIDER_unload() being fully effective #18254 - OPENSSL_strcasecmp build, cleanup, and initialization fixes #18282 - Always try to construct methods as new provider might be added #18269 - QUIC empty protocol implementation #18307 - ossl_namemap_name2_num: Avoid unnecessary OPENSSL_strndup(). #18341 - High level overview of QUIC Implementation #18406 I also took 1 day off this month. -- Tomáš Mráz, OpenSSL
Re: HPKE PR process question
On 23/05/2022 22:41, Stephen Farrell wrote: Hi, Back in November 2021 (~6 months ago) I created a PR [1] suggesting an implementation of RFC 9180. In discussion, the "need OMC decision" tag was added to the PR on Dec 14th. Since then, I have heard nothing at all and so far as I can see, from bits of the openssl-project list archive that I've checked, the OMC has had no discussion of this PR at all. Sorry that it has taken so long to get to this point. I assure you that the OMC have been discussing this PR and have now voted to lift the hold on it (which I have now done). Matt So, now I'm wondering how to make process-progress with this PR - can you assist or point me at the correct place to ask? (I can start a thread on openssl-users I guess if that's better?) Please note that this is about trying to unblock the process - the details of HPKE APIs are separate. (I remain happy to do work to get my code in a shape that the project likes, but to be honest, 6 months of seeming process-blockage with no feedback is a tad de-motivating.) Thanks, Stephen. [1] https://github.com/openssl/openssl/pull/17172
Monthly Status Report (May 2022)
Apart from normal business, attending daily standup meetings, attending OTC meetings, sprint planning meetings, etc., key activities this month: - Wrote up discussion of options for BIO_dgram API - PR #18238 (synthesized API proposals and DDD diffs into single PR) - PR #18270 (BIO_dgram sendmmsg/recvmmsg implementation work) - Updated lhash deprecation PR to implement chosen option - Setup YouTrack instance - Backported a bug fix to 1.0.2 for a premium support customer - PR #18305 fixing #18243 and #18242 (dev/release.sh --release) - PR tools#117 fixiing tools#116 (addrev release mode) - PR to fix Git hooks (release mode) - PR #18320 porting 1.1 EC compression compatibility tests to 3.x and incorporating changes from #16624 - Investiigated #18226 (OSSL_LIB_CTX_load_config thread safety) - PR #18323 (move modules lists to OSSL_LIB_CTX) - PR #18331 (make OSSL_LIB_CTX_load_config thread safe) fixing #18226 - Proposed deprecating long (#18338, technical-poliicies#51) - Moved YouTrack instance to production - Setup VCS integrations with YouTrack - Patched YouTrack GitHub importer to work with GHE and imported issues - PR #18382 (QUIC wire format support) - Implemented BIO_dgram_pair - Attended SSL object structure workshop - Attended 3.1 release and risk assessment meetings