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
It seems, that several (D)TLS libraries are now mandating RFC 5746 and disable the default "legacy support" for peers without RFC 5746. Californium 3.8 will therefore provide a implementation of a minimal version. Means, it indicates the secure renegotiation, but still don't support renegotiation at all.
Not sure, if RFC5746 is required for Californium 2. Leshan 1 seems to be one of the last projects, which requires that. So, if some of the leshan users/developers wants to back-port the PR, feel free to contribute it.
The text was updated successfully, but these errors were encountered:
I guess ideally this would be better to have it in Californium v2.x for Leshan v1.x.
I didn't plan to backport it at short term.
So I let this open to the attention of Leshan v1.x users who could need this.
Just for information:
It seems, that several (D)TLS libraries are now mandating RFC 5746 and disable the default "legacy support" for peers without RFC 5746. Californium 3.8 will therefore provide a implementation of a minimal version. Means, it indicates the secure renegotiation, but still don't support renegotiation at all.
See tinydtls - openssl 3.1, Californium PR 5746, and Californium -Scandium - README - RFC5746
Not sure, if RFC5746 is required for Californium 2. Leshan 1 seems to be one of the last projects, which requires that. So, if some of the leshan users/developers wants to back-port the PR, feel free to contribute it.
The text was updated successfully, but these errors were encountered: