Skip to content
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

Closed
hug-dev opened this issue Jul 6, 2020 · 0 comments · Fixed by #39
Closed

Have a feature only using the PSA interface #38

hug-dev opened this issue Jul 6, 2020 · 0 comments · Fixed by #39
Assignees
Labels
enhancement New feature or request

Comments

@hug-dev
Copy link
Member

hug-dev commented Jul 6, 2020

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 and static 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 and psa-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 is implementation-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. Or interface.

@hug-dev hug-dev added the enhancement New feature or request label Jul 6, 2020
@hug-dev hug-dev self-assigned this Jul 9, 2020
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
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant