-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DTLS Fingerprints in SDP Offer/Answer are not verified #1708
Comments
Hey @gaukas We do have a test for this |
Hey @gaukas what browser are you using to test? I believe the remote peer isn't the one properly asserting. thanks |
I am not using any browser. The |
It may not be that simple because I tried to mess with both fingerprints in offer and answer. The data channel was still created successfully. |
@Sean-Der but thank you for the fast response! I really appreciate it. Please let me know if there's anything else I could help with. |
Ah I see. So the issue is that we set PeerConnectionState to failed, but we don't actually tear down the connections. I will fix that and tag a new release. This probably even warrants a CVE! If you are interested, good for resume and helps people update quicker. |
Thank you @Sean-Der! I'm glad that this issue could be helpful to the project.
|
Before we would set the PeerConnection to failed, but we would leave the DTLSTransport. This means that a user could still interact with the other transports. Relates to #1708
Before we would set the PeerConnection to failed, but we would leave the DTLSTransport. This means that a user could still interact with the other transports. Relates to #1708
Before we would set the PeerConnection to failed, but we would leave the DTLSTransport. This means that a user could still interact with the other transports. Relates to #1708
Thanks for the fast response! Now I see the problem has been fixed. |
Your environment.
What did you do?
data-channels-create
anddata-channels
from example.data-channels
data-channels
intodata-channels-create
What did you expect?
The built-in fingerprints verification should throw an error and therefore prevent the data-channel from being established.
What happened?
The data channel was created as usual.
The text was updated successfully, but these errors were encountered: