Open
Conversation
fippo
commented
Mar 26, 2026
| stream->require_cryptex = enable != 0; | ||
| break; | ||
| case ssrc_any_inbound: | ||
| case ssrc_any_outbound: { |
Contributor
Author
There was a problem hiding this comment.
not clear what the behavior should be for ssrc_any_outbound, maybe return srtp_err_status_bad_param?
allowing applications to reject packets not using cryptex using srtp_set_stream_require_cryptex(...) as described in https://datatracker.ietf.org/doc/html/rfc9335#section-5.2 Fixes cisco#804 (for 2_x_dev)
fippo
force-pushed
the
require-cryptex_2x
branch
from
696f132 to
78e0b8b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
allowing applications to reject packets not using cryptex using
srtp_set_stream_require_cryptex(...)
as described in
https://datatracker.ietf.org/doc/html/rfc9335#section-5.2
Fixes #804 (for 2_x_dev)