Skip to content

Non-string auth values are not compatible with the agent. #760

@Isaac-Matthews

Description

@Isaac-Matthews

If a TPM has been set up with a non-string auth value, for eaxmple by running:
tpm2_changeauth -c E "hex:0000DF0237BE41C0E0124CAAD0A619B29B8E3EE4173521656729C6F339DBC449"
the keylime agent is not compatible with the TPM as there is no way provide this value.

The current method for processing auth values set by the config file or environment variables can be found here, this only works for simple string auth values.

A possible fix could be if "hex:" is at the start of a provided auth value it should be interpreted as a hex auth value, this is how tpm2 tools currently works.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions