Priorities for OpenSSL 3.6
The question about priorities for the 3.6 release has been asked: https://openssl-communities.org/d/HCdTYIoN/priorities-for-3-6
What priorities do the committers think are beneficial?
Are there any other items you think should be added to the list?
My focus is on DTLS-1.3 so it is good to see it on the list. Development is currently stalled because of lacking review activity. With all of the PRs merged the implementation is able to interop with Wolfssl and Mozilla implementations, so I would count the implementation as fairly mature.
I hope that DTLS-1.3 being on the list will help PR reviews to have priority.
I'd support constant BIGNUM
It would be nice that the list would include links to issues, where that would include more details, or subitems. For instance, I would like to be able to do io uring with quic for both transmit and receive, with 0 copies (except encryption/decryption). Is that meant with performance improvements?
@Kurt Roeckx, agreed that would have been useful.
Do we want a poll here to formally select items or is everyone happy with me summarising the expressed opinions?
We could also add more fuzzers. Looking at the coverage, at least CMS, pkcs12 and http could use one.
I've summarised the responses on the original thread. Thanks for the input. I think that additional feedback should be on that thread rather than this one.
I can not directly comment in that thread
The idea is to comment in the communities you are registered in - so comments here or in any of the other communities you are a member of are welcome and entirely appropriate. The BAC representative for the particular community you comment in is the one that is expected to make sure the community input makes it into consideration for the BAC for what advice they provide.
Apologies Kurt, I had no idea that that thread was restricted. Comment here and I'll summaries and pass along.
I would vote for:
Hybrid/Composite PQC signature
Providers/fetching/decoders performance improvements
Simplified CLI
Documentation related stuff
BTW: Is it possible to change the comment list in a 'newest-on-top' style. It is inconvenient to scroll to the bottom if the list is very long...
IMO the best way would be to do a ranged vote like Nicola did for the Academics community: https://openssl-communities.org/d/dKyeVJG3/foundation-priorities-for-3-6/2
Item removed
Having a single unified list of items to vote for across the communities seems like a reasonable ask before calling such votes. I don't think we're there yet.
Nonetheless, I can raise a poll.
Keep in mind that there is a separate BAC for the Foundation and the Corporation and we expect the priority lists to actually be different. There is no expectation of a unified list. Nor do we expect each community to have the same view on priorities.
Taking all the community input and working through to make a recommendation (Foundation BAC to Foundation Board and Corporation BAC to Corporation Board) is the process.
The discussions are good to have and community input great to see - but we have to balance the different views from the different communities and to the Foundation and to the Corporation.
They won't be the same list.
Are you suggesting that two polls should be run per community? That's crazy. The community doesn't change and, for the most part, the BAC representative doesn't either. The communities are also not split by Corporation and Foundation, they are combined. This doesn't mean that the two BACs need to make the same decisions as to priority -- I agree with you that the two outcomes will be different. I don't think this distinction should spill down to the community polling.
By unified I meant that the questions asked of each community should be consistent and the poll used should be the same. Nicola's questions aren't exactly the same as the ones I'm going to poll (I split a couple in two). I am also going to use a score poll rather than a ranked choice one because sorting 25+ options into your preferred order is a right pain and laziness will take over after the first few items. It's even more painful when you have to scroll the window to put an item where you want it and you can't drag and scroll at the same time.
@Paul Dale
OT: I also originally thought I could limit the selected options to ten, or at least that is what the loomio interface led me to believe, but the setting about available choices apparently did not apply. Sharing experiences about how to run these polls can be helpful as well!
Working together on these polls makes a lot of sense to me as does learning from each other as we go. There will be some tweaking for the different communities I expect but the basic answers should mostly align.
Item removed
It seems the link to the poll is somehow lost so I am repeating it here:
https://openssl-communities.org/p/8lj6EgwJ/priorities-for-openssl-3-6-and-beyond
The results are in and indicate two clear leaders in the wants list.
I've used the median response instead of the mean for each category because the former is more robust against extreme values. It makes small differences to the ordering but it better highlights the strength of the desire for the first two items.
Thanks to those that voted, your input will be useful.
Good to see BIGNUM on the list, would really like to see this tackled.
Anythign related to Performance, security and testing are high priority.
Other things..
- ABI testing of assembly (See issue #21522)
- Power On Self Tests to be configured to run on first use? (There is a potential hit on every call if this needs to be locked or atomic_load?)
- Hybrid PQ Signatures
- Next round of PQ algorithms?