>>>>> "Christian" == Christian Ehrhardt <email address hidden> writes:
Christian> Reproducible in local autopkgtest
Let me make sure I'm understanding.
You are saying that prior to penssl 3, the test works, but with
openssl3, the test fails?
What is the ssl version in the successful tests?
For example from the failing test we have:
OpenSSL: TX ver=0x303 content_type=22 (handshake/client hello)
What's the txver from that message in the successful test?
Unfortunately, EAP-TTLS is a bit sensitive to the TLS protocol version
in use for some annoying standardization reasons.
It looks like things are failing on the server side.
The autopkgtest produces the freeradius log (which is admittedly huge)
as a test artifact.
Could I get a pointer to a failing freeradius log?
I'm also going to bring this bug to the attention of Moonshot upstream.
>>>>> "Christian" == Christian Ehrhardt <email address hidden> writes:
Christian> Reproducible in local autopkgtest
Let me make sure I'm understanding.
You are saying that prior to penssl 3, the test works, but with
openssl3, the test fails?
What is the ssl version in the successful tests?
For example from the failing test we have:
OpenSSL: TX ver=0x303 content_type=22 (handshake/client hello)
What's the txver from that message in the successful test?
Unfortunately, EAP-TTLS is a bit sensitive to the TLS protocol version
in use for some annoying standardization reasons.
It looks like things are failing on the server side.
The autopkgtest produces the freeradius log (which is admittedly huge)
as a test artifact.
Could I get a pointer to a failing freeradius log?
I'm also going to bring this bug to the attention of Moonshot upstream.