<html><head><style>pre,code,address {
margin: 0px;
}
h1,h2,h3,h4,h5,h6 {
margin-top: 0.2em;
margin-bottom: 0.2em;
}
ol,ul {
margin-top: 0em;
margin-bottom: 0em;
}
blockquote {
margin-top: 0em;
margin-bottom: 0em;
}
</style></head><body><div>Hi,</div><div><br></div><div>To do this, you need to modify the dtls plugin to give the right profiles to OpenSSL, look at the call to SSL_CTX_set_tlsext_use_srtp(), then search for the enum that reads it out to the SRTP elements (which already support AES-256). You </div><div><br></div><div>And then we'd need to add an API to webrtcbin to select it.</div><div><br></div><div>Olivier</div><div><br></div><div>On Fri, 2023-11-10 at 18:11 +0100, Laszlo Molnar via gstreamer-devel wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I want to achieve AES-256 encryption with webrtcbin (so webrtcbin uses AES-256-encoded SRTP packets). As I see from the source code (correct me if I'm wrong) webrtcbin uses DTLS and that only has AES-128. Is it possible to change this? To make a pipeline that uses an AES-256 encoder and disable webrtcbin's DTLS encoding? Any solution would work as long as it achieves AES-256.</div><div><br></div><div>Thanks!</div></div></blockquote><div><br></div><div><span><pre>-- <br></pre><pre>Olivier Crête
olivier.crete@collabora.com
Multimedia Lead
</pre></span></div></body></html>