how to disable Dtls Srtp on browser?

140 views
Skip to first unread message

garry li

unread,
Jul 31, 2020, 6:55:33 AM7/31/20
to discuss-webrtc
how to disable Dtls Srtp on browser?

Philipp Hancke

unread,
Jul 31, 2020, 6:57:02 AM7/31/20
to discuss...@googlegroups.com
You can do that for debugging in Chrome beta and canary:
You can not do that in stable. That is intentional.

Am Fr., 31. Juli 2020 um 12:55 Uhr schrieb garry li <garr...@gmail.com>:
how to disable Dtls Srtp on browser?

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/b6ea1a31-b080-4cbb-bad4-577c245673abo%40googlegroups.com.

garr...@gmail.com

unread,
Jul 31, 2020, 7:18:39 AM7/31/20
to discuss-webrtc
Sorry, I think the description of my question isn't accurate!  

When I test janus demo and open "chrome://webrtc-inernals",  I saw this message 
" 
 { 
    iceServers: [stun:stun.l.google.com:19302], 
    iceTransportPolicy: all, 
    bundlePolicy: balanced, 
    rtcpMuxPolicy: require, 
    iceCandidatePoolSize: 0, 
    sdpSemantics: "unified-plan” 
}, 
{
    advanced: [
        {
            enableDtlsSrtp: {
                  exact: true
            }
        }
    ]
}
"
but I don't find "enableDtlsSrtp" option in webrtc standardization. 

Whether I can change this option to false or not?  And How about to do this?

Alexander Abagian

unread,
Aug 10, 2020, 1:57:09 PM8/10/20
to discuss-webrtc
Hi,

This flag displays if the RTCPeerConnection was configured to use DTLS/SRTP with fingerprints or clear SRTP with crypto. Available in Chromium based browsers only.


let peerconstraints = {
    optional: [{DtlsSrtpKeyAgreement: true},
               {googDscp: true}]  // QoS related
};
this._dpc = new RTCPeerConnection(serverConfig, peerconstraints);

Harald Alvestrand

unread,
Aug 10, 2020, 2:02:20 PM8/10/20
to discuss...@googlegroups.com
This flag is a "feature" we actively want to remove. DtlsSrtp is mandatory in standard webrtc.

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/f1059672-eb9e-407b-989e-302697b08222o%40googlegroups.com.

Harsha. R

unread,
Aug 10, 2020, 2:40:29 PM8/10/20
to discuss...@googlegroups.com
I agree DTLS based key exchange is mandatory as per webrtc standards.
But I would request that it be allowed to be configurable - DTLS key exchange caused media bursts, with large packet sizes -  that not all radio/LTE bearers were/are able to effectively handle. 

Regards
Harsha R




To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAOqqYVEMc_kK-tZ7YfEhHOXa37BO%2Ba91iY8PxM%2Bf_u4g-WrWEw%40mail.gmail.com.

Sean DuBois

unread,
Aug 10, 2020, 3:05:24 PM8/10/20
to discuss...@googlegroups.com
SRTP has a NULL Cipher and is really easy to enable in you control both sides!

If you only want to do JS not much you can do I think.

thanks 

On Aug 10, 2020, at 11:40, Harsha. R <harsha.ra...@gmail.com> wrote:



Philipp Hancke

unread,
Aug 10, 2020, 3:08:26 PM8/10/20
to discuss...@googlegroups.com
ec certificates are typically ~700 bytes (for the whole dtls hello et al) which is smaller than the typical video keyframe packet so what is the problem here?

To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CANUSVwfifpYRWOSuqbtF9-SP0eVOymXsj1j%3DWChQbtKQmCWoag%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages