[jitsi-dev] Chrome 49 will be out soon...


#1

I'd like to be sure that my build of libjitsi won't fail due to their
latest updates in Chrome, for instance DTLS 1.2 is now fully deployed for
WebRTC in Chrome, the default DTLS cipher suite is now
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.

I already override the default config in libjitsi to use SHA256, but will
DTLS 1.2 be an issue?

M49 Release notes:
https://groups.google.com/forum/#!topic/discuss-webrtc/mcApW-3YADI

Regards,
Paul


#2

I don't expect so, it runs fine with Canary.

Boris

···

On 01/02/16 18:03, Mondain wrote:

I'd like to be sure that my build of libjitsi won't fail due to their
latest updates in Chrome, for instance DTLS 1.2 is now fully deployed
for WebRTC in Chrome, the default DTLS cipher suite is now
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.

I already override the default config in libjitsi to use SHA256, but
will DTLS 1.2 be an issue?


#3

This has already been shipped on January 11th in M47 and M48 which has taken off over the weekend:
https://groups.google.com/forum/#!searchin/discuss-webrtc/psa$20dtls/discuss-webrtc/s8IzGI53Gc4/f3uuusPJEwAJ

···

Am 01.02.2016 um 16:03 schrieb Mondain:

I'd like to be sure that my build of libjitsi won't fail due to their
latest updates in Chrome, for instance DTLS 1.2 is now fully deployed for
WebRTC in Chrome, the default DTLS cipher suite is now
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.

I already override the default config in libjitsi to use SHA256, but will
DTLS 1.2 be an issue?


#4

I've not encountered any real issues so far as I can tell in Chrome 48,
except that my VP8 stream doesn't seem to appear correctly in the ssrc
information on webrtc-internal, but that may not be related to any of this;
I assume its a bug in my code.

···

On Mon, Feb 1, 2016 at 10:39 PM Philipp Hancke <fippo@goodadvice.pages.de> wrote:

Am 01.02.2016 um 16:03 schrieb Mondain:
> I'd like to be sure that my build of libjitsi won't fail due to their
> latest updates in Chrome, for instance DTLS 1.2 is now fully deployed for
> WebRTC in Chrome, the default DTLS cipher suite is now
> TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
>
> I already override the default config in libjitsi to use SHA256, but will
> DTLS 1.2 be an issue?

This has already been shipped on January 11th in M47 and M48 which has
taken off over the weekend:

https://groups.google.com/forum/#!searchin/discuss-webrtc/psa$20dtls/discuss-webrtc/s8IzGI53Gc4/f3uuusPJEwAJ

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev