libjitsi: DTLS 1.2 support is missing

WebRTC does support DTLS 1.2, but libjitsi is only support DTLS 1.0. There is some old comment in code regarding DTLS 1.2 support which might be irrelevant anymore and DTLS 1.2 support could be added to libjitsi.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 33 (17 by maintainers)

Most upvoted comments

Putting more pressure on the developers is not going to help. This is being worked on.

FYI DTLS 1.0 has been re-enabled in Firefox Beta 75 https://bugzilla.mozilla.org/show_bug.cgi?id=1623511

We leave it off in Nightly as a reminder that when the world reaches a new normal we still plan to remove it eventually. This also allows for easier testing 😃

My test shows that packages org.bouncycastle.crypto.tls.* works with DTLS1.2 - have to be updated to 1.61 (in maven already) Changes in libjitsi is just increase protocol version

protected ProtocolVersion getMaximumVersion()
    {
        return ProtocolVersion.DTLSv12;

Such changes fixes this https://github.com/jitsi/jitsi-videobridge/issues/798

We’re definitely still keeping the M74 timeline in mind here. I looked at this again last week and we identified some complications with upgrading the BC version due to the way our maven poms were set up. That’s (hopefully) fixed now and I’ll be looking at this again today/next week, but the implementation itself will take more time.

IIRC @bbaldino is tracking this with the M74 timeline in mind.

We are aiming this week … as soon as possible, currently working on that.

if this is about the jvb, jvb2 supports dtls 1.2 and the intention is to switch to that for the debian stable package. I believe there’s consensus to release jvb2 as debian stable, it’s just a matter of the right people finding the time to do it /cc @damencho

libjitsi is not used anymore in jvb2. And jvb2 supports DTLS 1.2. We are working on updating the stable channel with the latest from unstable.

We don’t collect installation data so we don’t know. JVB 2 hasn’t made it to our stable repository yet, but that should happen very soon.

@mstyura good to know, thanks. If we/I get to that before anyone else, we’ll know to focus on using the new APIs instead of trying to make 1.2 work with the current ones.