-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have a feature only using the PSA interface #38
Labels
enhancement
New feature or request
Comments
hug-dev
added a commit
to hug-dev/rust-psa-crypto
that referenced
this issue
Jul 9, 2020
For some use-cases, for example building a Secure Element driver, it is only needed to have an abstraction over the PSA Crypto API include files but not the operations. The new interface feature is made for that. Fix parallaxsecond#38 Signed-off-by: Hugues de Valon <hugues.devalon@arm.com>
hug-dev
added a commit
to hug-dev/rust-psa-crypto
that referenced
this issue
Jul 13, 2020
For some use-cases, for example building a Secure Element driver, it is only needed to have an abstraction over the PSA Crypto API include files but not the operations. The new interface feature is made for that. Fix parallaxsecond#38 Signed-off-by: Hugues de Valon <hugues.devalon@arm.com>
hug-dev
added a commit
to hug-dev/rust-psa-crypto
that referenced
this issue
Jul 14, 2020
For some use-cases, for example building a Secure Element driver, it is only needed to have an abstraction over the PSA Crypto API include files but not the operations. The new interface feature is made for that. Fix parallaxsecond#38 Signed-off-by: Hugues de Valon <hugues.devalon@arm.com>
hug-dev
added a commit
to hug-dev/rust-psa-crypto
that referenced
this issue
Jul 14, 2020
For some use-cases, for example building a Secure Element driver, it is only needed to have an abstraction over the PSA Crypto API include files but not the operations. The new interface feature is made for that. Fix parallaxsecond#38 Signed-off-by: Hugues de Valon <hugues.devalon@arm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the Secure Element Driver use-case, PSA Crypto is only needed for its interface (the include files in
include/psa
): the types, the values, the macros andstatic inline
methods.It should not need linking with the actual PSA Crypto implementation but only need its include files.
For that use-case, and similar ones, we should have a special feature on
psa-crypto
andpsa-crypto-sys
which make them expose all the PSA Crypto interface, without the operations.MBEDTLS_INCLUDE_DIR
env var must be passed for that feature as part of the interface isimplementation-defined
.I am not sure fo the name of the feature. If the use-case is only for the SE driver, it could be the
se-driver
feature. Orinterface
.The text was updated successfully, but these errors were encountered: