keylime / keylime/rust-keylime
API version mismatch for emulated TPM setup
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 162
- Forks
- 76
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 3
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the agent code containing the hard-coded API_VERSION and the keylime-vagrant-ansible-tpm-emulator setup. Compare the agent's v2.2 registrar request with the registrar's reported current and supported versions. Done means the emulator setup and agent use compatible API versions and registration succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100