You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
compat.sh doesn't run any interoperability test against OpenSSL with a CCM cipher suite.
Observed in several ways, both in 2.28 and development (and very likely 3.6 as well, but I haven't checked):
Grab an outcome file from a nightly run and <outcomes.csv grep -E ';compat;(O->m|m->O)' | grep CCM — there are no hits, whereas there are hits for CBC and GCM.
Run tests/compat.sh -t tls12 (or dtls12) in the default configuration: there are m->m and G->m and m->G tests with CCM and CCM-8, but no m->O or O->m. There are m->O or O->m with other ciphers, but not CCM.
OpenSSL acquired CCM cipher suite support in version 1.1.0, so our default OpenSSL on the CI (the antique OpenSSL 1.0.2g) doesn't have it. But OPENSSL_NEXT (1.1.1a) does have it, so I would expect at least some CCM tests to run.
The text was updated successfully, but these errors were encountered:
compat.sh
doesn't run any interoperability test against OpenSSL with a CCM cipher suite.Observed in several ways, both in 2.28 and
development
(and very likely 3.6 as well, but I haven't checked):<outcomes.csv grep -E ';compat;(O->m|m->O)' | grep CCM
— there are no hits, whereas there are hits forCBC
andGCM
.tests/compat.sh -t tls12
(ordtls12
) in the default configuration: there arem->m
andG->m
andm->G
tests withCCM
andCCM-8
, but nom->O
orO->m
. There arem->O
orO->m
with other ciphers, but not CCM.OpenSSL acquired CCM cipher suite support in version 1.1.0, so our default OpenSSL on the CI (the antique OpenSSL 1.0.2g) doesn't have it. But
OPENSSL_NEXT
(1.1.1a) does have it, so I would expect at least some CCM tests to run.The text was updated successfully, but these errors were encountered: