-
Notifications
You must be signed in to change notification settings - Fork 52
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
API version mismatch for emulated TPM setup #833
Comments
ramrattle
changed the title
API version mismatch for emulate TPM setup
API version mismatch for emulated TPM setup
Aug 22, 2024
I'm not aware of that emulator. It seems it is using a very old version of keylime. @mpeters Is that something we still maintain? If so, could you please check if it is possible to update Keylime there? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was trying https://github.com/keylime/keylime-vagrant-ansible-tpm-emulator, the registar starts with the version 2.1 but the default API version that agent looks for is 2.2 in registar URI which is not there, so registration is failing
registrat
2024-08-22 10:13:21.527 - keylime.registrar - INFO - Current API version 2.1
2024-08-22 10:13:21.527 - keylime.registrar - INFO - Supported older API versions: 1.0, 2.0
2024-08-22 10:13:21.527 - keylime.registrar - INFO - Deprecated API versions (soon to be removed): 1.0
Agent
keylime_agent
Error: Registrar { addr: "http://127.0.0.1:8890/v2.2/agents/d432fbb3-d2f1-4a97-9ef7-75bd81c00000", code: 400 }
Agent code where api is hard coded
pub const API_VERSION: &str = "v2.2";
solution : should we rebase the code for the emulator repo?
The text was updated successfully, but these errors were encountered: