PoC of video frames encryption using AES-CTR #1096
Draft
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
This PoC demonstrates the use of AES-CTR encryption of video frames transmitted between the Tx and Rx sessions. It shows that video frames can be treated as binary blobs that could be encrypted. The PoC uses https://github.com/intel/intel-ipsec-mb for the AES-CTR encryption. Sample file can be generated with: ``` ffmpeg -an -y -f lavfi -i \ testsrc=d=5:s=1920x1080:r=25,format=yuv422p10be -f rawvideo \ /tmp/yuv422p10le.yuv ``` To run PoC: ``` ./tests/tools/RxTxApp/build/RxTxApp --config_file \ config/tx-rx-encryption.json --test_time=10 ``` RxTxApp sends the input file in a loop, the output file can have data from the input file written to in multiple times. known issues: - There is no key exchange mechanism implemented in this PoC, the key is hardcoded in the code. - Transport format has to be the same as the input format. Mismatch causes corruption of the data - It works only for uncompressed video formats. (not for SMPTE 2110-22) - Everything is done in an application instead of in the library
Sakoram
force-pushed
the
AES-CTR_encryption_PoC
branch
from
4923e8b to
51c53e9
Compare
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.
This PoC demonstrates the use of AES-CTR encryption of video frames transmitted between the Tx and Rx sessions. It shows that video frames can be treated as binary blobs that could be encrypted. The PoC uses https://github.com/intel/intel-ipsec-mb for the AES-CTR encryption.
Sample file can be generated with:
To run PoC:
RxTxApp sends the input file (
/tmp/yuv422p10be.yuvis used by tx-rx-encryption.json) in a loop,the output file (
/tmp/out.yuv) can have data from the input file written to in multiple times.known issues:
is hardcoded in the code.
causes corruption of the data