Skip to content
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.

Document how to start a new agent after 6.3.0 mtls changes #75

Open
aplanas opened this issue Feb 7, 2022 · 4 comments
Open

Document how to start a new agent after 6.3.0 mtls changes #75

aplanas opened this issue Feb 7, 2022 · 4 comments
Assignees

Comments

@aplanas
Copy link

aplanas commented Feb 7, 2022

After this commit: keylime/keylime@70a2f8e that is part of keylime 6.3.0, an agent cannot be started until the CA certificate (that is usually living in the register / verifier node) is copied into the agent node.

We should document this step, together with strategies that allow easy new agent deployments.

@aplanas
Copy link
Author

aplanas commented Feb 7, 2022

cc: @THS-on

@aplanas
Copy link
Author

aplanas commented Feb 7, 2022

I updated the doc in the openSUSE MicroOS portal: https://en.opensuse.org/Portal:MicroOS/RemoteAttestation#Keylime_agent

@mpeters
Copy link
Member

mpeters commented Feb 7, 2022

I thought the upgrade would continue to work with previous agents on non-mtls so there would exist an upgrade path. Maybe there's a bug that needs to be fixed @THS-on ?

@THS-on
Copy link
Member

THS-on commented Feb 7, 2022

@mpeters the old agents (<6.3) still work, but we haven't updated the documentation for the 6.3 agents which now require a the CA for the mTLS connections.

@THS-on THS-on self-assigned this Apr 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants