[core] Fix crypto mode auto for listener sender. #2711
Merged
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.
An SRT listener configured with
SRTO_CRYPTOMODE=Auto
creates a sender buffer before negotiating the crypto mode. When the sender buffer is created, it needs to know the mode to save the size of the authentication tag. Thus the sender buffer is created as if a regular AES-CTR mode is to be used.This PR moves the allocation of RCV and SND buffers after the negotiation is done and the crypto control is configured.
The exception is the rendezvous mode where buffers are still created right after the crypto control (although previously they were allocated before the crypto control).
Closes #2703 (includes).
TODO