Copyright (C) 2021, Axis Communications AB, Lund, Sweden. All Rights Reserved.

The Signed Video Framework handles both the signing part as well as the validation part. All public APIs needed are located in includes/.

The APIs needed are signed_video_common.h and signed_video_auth.h. To validate a H.264, H.265 or AV1 video you need to split the video into NAL Units/OBUs. For a detailed description and example code see signed_video_auth.h or look at the validator in the signed-video-framework-examples repository.

The APIs needed are signed_video_common.h and signed_video_sign.h. To sign a H.264, H.265 or AV1 video you need to split the video into NAL Units/OBUs. Before signing can begin you need to configure the Signed Video session. Setting a private key is mandatory, but there are also possibilities to add some product information and what level of authentication to use. The public key, needed for validation, is automatically added to the stream.

The Signed Video Framework generates SEI/OBU Metadata frames including signatures and other information. Getting them and instructions on how to add them to the current stream are handled through the API signed_video_get_sei(). Note that the framework follows the Access Unit format of H.264, hence SEI frames must prepend the current picture frame.

For a detailed description and example code see signed_video_sign.h or look at the signer in the signed-video-framework-examples repository.

There is currently no signing plugin management in the Signed Video Framework. It currently builds with the unthreaded-signing/plugin.c. The APIs signed_video_signing_plugin.h and signed_video_openssl.h are for plugins. For more information see lib/plugins/.