-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-10.1
-
crypto-policies-20250714-1.git95bf40e.el10
-
No
-
Low
-
2
-
rhel-security-crypto-spades
-
20
-
27
-
2
-
False
-
False
-
-
Yes
-
Crypto25August, Crypto25September
-
-
Pass
-
Enabled
-
Automated
-
Enhancement
-
-
Proposed
-
Unspecified
-
Unspecified
-
Unspecified
-
None
OpenSSL 3.5 features new syntax for group selection, asterisks and slashes:
- asterisks before group names signify that the client must send key_share for this group
(note, no more than 4 asterisks are allowed at the same time, or openssl starts ignoring you) - slashes subdividing the group list signify that the server must only resort to using the groups from the next slashed group subdivision if none of the groups from the previous one are supported by the client
We should use this functionality to support the following sane default we're after:
- divide the groups into post-quantum (hybrid, pure) and classical ones, with the post-quantum ones given priority over the classic ones because they provide new security properties
- "star" the leftmost post-quantum and the leftmost classic group for HRR-less negotiation with the most common servers out there
We plan to seek out this default behaviour for other libraries as well, no matter whether configured through crypto-policies or implemented as a library default.
Compare and contrast https://issues.redhat.com/browse/RHEL-91144: here we introduce no additional configurability, at least for now.
- is caused by
-
RHEL-91144 Support specifying key_shares to send [rhel-10.1]
-
- Closed
-
- links to
-
RHBA-2025:148296 crypto-policies bug fix and enhancement update