Skip to content

Fix typo introduced by PR 559#562

Merged
pabuhler merged 1 commit intocisco:masterfrom
lminiero:typo-fix
Sep 13, 2021
Merged

Fix typo introduced by PR 559#562
pabuhler merged 1 commit intocisco:masterfrom
lminiero:typo-fix

Conversation

@lminiero
Copy link
Copy Markdown
Contributor

This PR fixes a typo introduced by #559, where for SRTP_AES_GCM_256 the returned length is SRTP_AES_ICM_256_KEY_LEN_WSALT instead of SRTP_AES_GCM_256_KEY_LEN_WSALT, which causes problems when SRTP sessions are created using AES-GCM-256.

@pabuhler
Copy link
Copy Markdown
Member

strange there was no test to catch this :(

@pabuhler pabuhler merged commit 40f3be0 into cisco:master Sep 13, 2021
@lminiero
Copy link
Copy Markdown
Contributor Author

strange there was no test to catch this :(

@pabuhler not sure, but my guess is this would have probably been tricky to catch using unit tests. We only noticed the issue when we were notified by someone using 2.4.1 about problems with srtp_unprotect on incoming RTCP on the server, but there were no reported failures in srtp_protect for outgoing RTP or RTCP for instance: when we worked on replicating the issue, we noticed media wouldn't work either, and that was because srtp_protect would "succeed", but then the browser would not render anything, because of failures to unprotect on that end.

@lminiero lminiero deleted the typo-fix branch September 14, 2021 09:53
seyednasermoravej pushed a commit to seyednasermoravej/libsrtp that referenced this pull request Nov 9, 2025
Fix typo introduced by PR 559
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants