Opened 7 years ago

Closed 7 years ago

Last modified 6 years ago

#1993 closed task (fixed)

Update bundled libSRTP version to enable AES-GCM on OpenSSL 1.1.0 or later

Reported by: nanang Owned by: bennylp
Priority: normal Milestone: release-2.7
Component: third-party Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported: no

Description

AES-GCM feature in libSRTP 1.5.4 (the latest 1.x release) has compatibility issue with OpenSSL 1.1.0 (see also ticket #1932). However in the current development source code, it seems to have some work on supporting OpenSSL 1.1.0, so when new version is released, it is better to update our bundled libSRTP.

Change History (7)

comment:1 Changed 7 years ago by nanang

  • Resolution set to fixed
  • Status changed from new to closed

In 5614:

Close #1993: Updated bundled libSRTP version to 2.1.0.

comment:2 Changed 7 years ago by nanang

In 5615:

Re #1993: Minor: cleaned up few more unused files.

comment:3 Changed 7 years ago by nanang

In 5617:

Re #1993: Slight improvement on simple SRTP key generator (when PJ_HAS_SSL_SOCK is not set).

comment:4 Changed 7 years ago by nanang

In 5618:

Re #1993: Updated sample apps streamutil.c/vid_streamutil.c as the new libsrtp removes hex_string_to_octet_string().

comment:5 Changed 7 years ago by nanang

In r5622: Updated configure script to enable AES-GCM with OpenSSL 1.1.0 after updating bundled libsrtp version.

comment:6 follow-up: Changed 6 years ago by ming

In 5656:

Re #1993: With the update of bundled libSRTP to 2.1, external SRTP needs to be of version 2.x as well. This changeset will allow external SRTP users the option to continue using their current version 1.x.

  • Also add autodetection of external SRTP version via the configure script.

Thanks to Alexander Traud for the report.

comment:7 in reply to: ↑ 6 Changed 6 years ago by ming

  • Tested with external SRTP version 2.1 and 1.6. Due to API changes in libSRTP, other versions may not directly work.
Note: See TracTickets for help on using tickets.