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

Integrate Véraison C/Rust client wrapper on server side #15

Open
paulhowardarm opened this issue Feb 10, 2023 · 0 comments
Open

Integrate Véraison C/Rust client wrapper on server side #15

paulhowardarm opened this issue Feb 10, 2023 · 0 comments
Assignees

Comments

@paulhowardarm
Copy link
Collaborator

Summary

The server side of the TLS stack (relying party) needs to call a Veraison challenge/response service endpoint in order to validate the KAT bundle that authenticates the client (attester). Currently, the KAT bundle is only being processed locally.

Details

For a PoC, it will not be necessary to fully integrate the Veraison client into the MbedTLS build process. It should be sufficient to require the person building the demo to have built the Veraison client using Cargo, which will produce a static library and a generated header file. These can be specified as build-time include and linker options for Mbed TLS.

The Rust/C client is available here as a single repo, and can be built trivially with cargo build. The mainline branch should suffice.

It is probably necessary to add a new command-line parameter to ssl_server2 to accept the HTTP endpoint of the challenge-response API.

There is some work needed to figure out exactly which parts of the existing code need to be replaced with the call to Veraison.

@paulhowardarm paulhowardarm converted this from a draft issue Feb 10, 2023
@paulhowardarm paulhowardarm moved this from Todo to In Progress in Attested TLS PoC Feb 24, 2023
@paulhowardarm paulhowardarm self-assigned this Feb 24, 2023
@paulhowardarm paulhowardarm moved this from In Progress to Done in Attested TLS PoC Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant