-
Notifications
You must be signed in to change notification settings - Fork 141
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
keylime_tenant seems to read verifier.conf #1541
Comments
When there is no
|
Does the tenant need mba at all?
This was added in c99103b:
|
@stefanberger I saw that the PR got closed without being merged, what was the reason for that and is this issue still there? |
The changes in that PR didn't work. |
In particular one ends up running into this kind of issue then:
|
Is your issue a feature request? If so, please raise it as an enhancement
Environment
Description
in keylime_tenant outout one can see that verifier.conf is read.
For example:
Previously, I have reported similar issue #1446, I don't know if this is related though.
Expected behavior vs. actual behavior
keylime_tenant should not access verifier.conf, probably even ca.conf
Steps to reproduce problem
The text was updated successfully, but these errors were encountered: