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
Hello.
Our application receives SDP offer from webrtc.rs and sets setup:active in the answer.
Then our application starts dtls handshake by sending client_hello with list of elliptic curve groups supported by our application.
I expect that webrtc.rs should find curves supported by itself in the received list and then continue handshake using the best curve supported by both sides.
I have noticed that webrtc.rs supports only P384, P256, X25519 curves and make sure that they are included in the client_hello curves list:
But during of handshake i have got the error:
warning: [webrtc::peer_connection::peer_connection_internal:654]: Failed to start manager dtls: invalid named curve
And tcpdump:
I did an investigation and looks like webrtc.rs just uses the first curve in the received list and forbids handshake if curve is not supported despite that supported curves are present in the list.
I suppose that the code which selects first curve is:
Hello.
Our application receives SDP offer from
webrtc.rs
and setssetup:active
in the answer.Then our application starts dtls handshake by sending
client_hello
with list of elliptic curve groups supported by our application.I expect that
webrtc.rs
should find curves supported by itself in the received list and then continue handshake using the best curve supported by both sides.I have noticed that
webrtc.rs
supports onlyP384
,P256
,X25519
curves and make sure that they are included in theclient_hello
curves list:But during of handshake i have got the error:
And tcpdump:

I did an investigation and looks like
webrtc.rs
just uses the first curve in the received list and forbids handshake if curve is not supported despite that supported curves are present in the list.I suppose that the code which selects first curve is:
webrtc/dtls/src/flight/flight0.rs
Lines 101 to 114 in 7611518
Also i did an experiment and sent P384 as first element of curves list and unsupported curve as second element. Handshake has been completed:
Could you please consider to implement searching of supported curve in received list instead of using first curve.
Thanks
The text was updated successfully, but these errors were encountered: