[core] Drop noenc packets if RcvKmState is "secured". #2921
Conversation
This file contains 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
maxsharabayko
added
Type: Maintenance
maxsharabayko
force-pushed
the
hotfix/km_secured_drop_noenc
branch
from
48847f8
to
d2096b8
Compare
Updated pktRcvUndecrypted description.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously unencrypted packets were being dropped in case AES-GCM mode was used.
With this change, they are being dropped if the KM connection state is "Secured".
It respects the SRTO_ENFORCED_ENCRYPTION option that allows connections without encryption, in which case the RCV KM state would be "Unsecured".