You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 8, 2022. It is now read-only.
Repository navigation
This repository was 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
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.
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 ?
@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.
Activity
aplanas commentedon Feb 7, 2022
cc: @THS-on
aplanas commentedon Feb 7, 2022
I updated the doc in the openSUSE MicroOS portal: https://en.opensuse.org/Portal:MicroOS/RemoteAttestation#Keylime_agent
mpeters commentedon 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 commentedon 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.