Hi Martin,
Let me clarify: remote node is acting as DTLS client and sends DTLS client
hello with DHE_RSA. Firefox replies with handshake failure.
What shall be done to solve this? I didn't get how the '2048-bit share' relates
to this. You also mentioned the RTCCertificate API, for which there i
Martin, just to double-check: by 'client' you mean WebRTC client, and not the
remote node which is sending the DTLS client hello towards FF, right?
Thanks,
Ors
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev
Thanks a lot Martin, will look into that!
Regards,
Ors
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-media
Hello,
I'm getting DTLS handshake failure basically with all FF versions (even with
latest nightly build) for a DTLS client hello with the following cipher suites:
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
Is this a known fault in FF?
Regards,
Ors
Thanks Eric.
According to: https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-02,
Chapter 5.1:
" As mentioned earlier in this section, Offers and Answers can contain
any set of candidates, which means that a trickle ICE session
description MAY contain no candidates at all. In such ca
Thanks Martin, but i suppose that doesn't mean that Firefox only includes these
two cipher suites in the ClientHello:
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
I remember seeing many more earlier, e.g. DHE-RSA and ECDHE-RSA. I know that
non-PFS ciphers are rem
Hi,
Can you tell me what is the reasoning behind this?
Thanks.
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-media
Where can i find information on how Firefox is selecting the cipher suite to be
used from the list of cipher suites it receives in DTLS ClientHello ?
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-media
8 matches
Mail list logo