[asterisk-bugs] [JIRA] (ASTERISK-29625) srtp cryptos accepted if not enabled

Benjamin Keith Ford (JIRA) noreply at issues.asterisk.org
Thu Sep 2 11:05:33 CDT 2021


     [ https://issues.asterisk.org/jira/browse/ASTERISK-29625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Keith Ford updated ASTERISK-29625:
-------------------------------------------

    Assignee: Jasper Hafkenscheid
      Status: Waiting for Feedback  (was: Triage)

Would you be interested in submitting your patch to Gerrit\[1]? Instructions on how to do so can be found here\[2].

\[1]: https://gerrit.asterisk.org/q/status:open
\[2]: https://wiki.asterisk.org/wiki/display/AST/Gerrit+Usage

> srtp cryptos accepted if not enabled
> ------------------------------------
>
>                 Key: ASTERISK-29625
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29625
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_srtp
>    Affects Versions: 18.6.0
>         Environment: Debian Buster with the default libsrtp 2.2.0.
>            Reporter: Jasper Hafkenscheid
>            Assignee: Jasper Hafkenscheid
>
> When compiled with {{HAVE_SRTP_256}} enabled (by configure), and without {{ENABLE_SRTP_AES_256}}, received crypto lines are still parsed and used.
> We experienced several devices that did not work happily with 256 bit encryption, such as certain Fritz!box, Grandstream and Tiptel. Either having no audio or have it be disrupted after a couple of minutes.
> The fix we applied is to use verify {{ENABLE_SRTP_AES_256}} as well as {{HAVE_SRTP_256}} are defined when parsing the SDP in {{res_sdp_crypto_parse_offer}}. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list