What
There are several options for interfacing NXP S32G in a score_provider:
AG_ALG, libhse, cryptodef, OpenSSL with AG_ALG engine.
Within this task, an afalg_provider will created (starting point: openssl provider)
which shows that the actual crypto operations can be handled by the Linux kernel
crypto API (i.e. , use sockets of type AF_ALG).
As it is a PoC, only the hash used cases will be supported.
Within provider_test, test_afalg_provider.cpp will be created.
Acceptance Criteria (DoD)
test_afalg_provider running on NXP EVB3 target.
Comparison execution time test_provider and test_afalg_provider
How
The openssl provider will be duplicated to afalg provider.
Initially, afalg_provider will do crypto operations with OpenSSL.
Step by Step, the calls to OpenSSL (e.g., EVB_Digest) will be redirected to the Linux kernel crypto interface.
What
There are several options for interfacing NXP S32G in a score_provider:
AG_ALG, libhse, cryptodef, OpenSSL with AG_ALG engine.
Within this task, an afalg_provider will created (starting point: openssl provider)
which shows that the actual crypto operations can be handled by the Linux kernel
crypto API (i.e. , use sockets of type AF_ALG).
As it is a PoC, only the hash used cases will be supported.
Within provider_test, test_afalg_provider.cpp will be created.
Acceptance Criteria (DoD)
test_afalg_provider running on NXP EVB3 target.
Comparison execution time test_provider and test_afalg_provider
How
The openssl provider will be duplicated to afalg provider.
Initially, afalg_provider will do crypto operations with OpenSSL.
Step by Step, the calls to OpenSSL (e.g., EVB_Digest) will be redirected to the Linux kernel crypto interface.