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

Testing OP-TEE Remote Attestation with Veraison compiled natively #1

Open
graziadonghia opened this issue Sep 5, 2024 · 2 comments

Comments

@graziadonghia
Copy link

Hello, I am trying to run your project with Veraison verification. While trying to compile Veraison with docker deployment, I encountered many errors that I couldn't fix, so I tried to compile it natively and it worked. At this point I want to ask whether it is possible to run the OP-TEE remote attestation with Veraison verification compiled natively.
Thank you in advance.

@kunisuzaki
Copy link
Contributor

Do you mean that you buiid OPTEE PTA for remote attestation?
Ather that you need to build
CA and TA https://github.com/iisec-suzaki/optee-ra/tree/main/attester/remote_attestation
Relying Party on other machine 1 https://github.com/iisec-suzaki/optee-ra/tree/main/relying_party
and set up Verifier (Variasion) on other machine 2.

@graziadonghia
Copy link
Author

Thank you. When I run the optee_remote_attestation command, I receive the following errors:
On the relying party:
Error forwarding request: Post "http://verification-service:8080/challenge-response/v1/newSession?nonceSize=32": dial tcp: lookup verification-service: Temporary failure in name resolution

On the normal world:
Failed to allocate Veraison client session. Error/log message: error decoding response body: expected value at line 1 column 1 Disposing client session

I guess these errors are related with the fact that the attester cannot connect to the verifier, even though it is active and running and the URL matches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants