Skip to content
This repository was archived by the owner on Feb 18, 2026. It is now read-only.
This repository was archived by the owner on Feb 18, 2026. It is now read-only.

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

Description

@dreemkiller

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.

Activity

  1. egrimley-arm commented on Jun 29, 2023

    @egrimley-arm
    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?

  2. dreemkiller commented on Jun 29, 2023

    @dreemkiller
    MemberAuthor

    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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions