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

Transition our PSA-Attestation client activity to use PARSEC #641

Open
dreemkiller opened this issue Jun 29, 2023 · 2 comments
Open

Transition our PSA-Attestation client activity to use PARSEC #641

dreemkiller opened this issue Jun 29, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@dreemkiller
Copy link
Member

Requested feature

Start using PARSEC for our psa-attestation client

Motivation
Using CCC projects is a priority, so this makes sense.
Also, our current psa-attestation client code is quite hacky.

Additional context
There may be some complications on this as we do a few dirty things with psa-attestation, so the transition might not be completely straightforward.

@dreemkiller dreemkiller added the enhancement New feature or request label Jun 29, 2023
@egrimley-arm
Copy link
Contributor

If Parsec is built with certain features, it depends on psa-crypto, which indirectly uses libmbedtls.a, which is also indirectly used by the mbedtls crate. Will this cause problems for us?

@dreemkiller
Copy link
Member Author

Possibly, especially if they are different versions. In the past, when we've had these problems (when we supported TrustZone, the OPTEE OS included an older version of mbedtls that didn't contain the psa-crypto API we were using), we linked against both versions, but changed the symbol names (using the objcopy --redefine-syms flag) so that both versions could be linked.

Another possibility: get PARSEC to use the mbedtls Rust Crate directly instead of relying on calls directly to the libmbedtls.a file.

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

No branches or pull requests

2 participants