Michael,
Thanks for answering my question.
Since the SHA-1 hash function is considered vulnerable, will there be an effort to modify the hard coded entry to one that isn’t as vulnerable?
Starting with version 56, Google Chrome will mark all SHA-1-signed HTTPS certificates as unsafe. Other major browser vendors plan to do the same.
Since we are using this for WebRTC it seems that a modification to the code is warranted.
Your thoughts?
Jerry Chinn
Telecom VoIP Specialist
NAVIS More Performance. More Profit.
tel 541-330-3562
From: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org]
On Behalf Of Michael Jerris
Sent: Wednesday, May 09, 2018 12:02 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] WebRTC using rtp_sdes_suites=AES_CM_128_HMAC_SHA1_80
on DTLS this setting is currently a no-op and the suites it uses are hard coded.
On May 9, 2018, at 2:21 PM, Mirko Brankovic <mirkobrankovic@gmail.com> wrote:
Hi,
I had a same problem.
Was debugging a different handshake problem, and wanted to try other chipers, but failed.
Looks like the setting is not applied at all, and would be nice to use cheeper (network wise) encroption
On Wed, May 9, 2018, 00:52 Aqs Younas <aqsyounas@gmail.com> wrote: