Karel Srot

I believe you are right. The question is how to approach it on keylime side. Either update some docs we have, maybe drop a comment to keylime.conf. Or maybe handle...

Hello, any plans to work on this RFE? Also, in addition to the screenshot above, it would be nice to see similar test case details for "similar test results from...

Hello, any updates on this one? Thank you.

Hello, thank you for accepting this issue. Just adding few comments: - There might be more option how to specify a filter that should be applied. One option could be...

Hi @maugustosilva , it seems we have very log test coverage for this newly introduced code. Would you mind proposing some e2e test scenario in https://github.com/RedHat-SP-Security/keylime-tests/issues/195 or possibly implement some...

Do we need to verify every single line from the IMA log? Let's say there are 100 records in the IMA log and we want to update keylime policy for...

From tests ``` keylime_verifier[4785]: 2023-02-27 17:37:30.909 - keylime.verifier - WARNING - POST returning 400 response. Exception error: 'ima_sign_verification_keys' keylime_verifier[4785]: 2023-02-27 17:37:30.910 - keylime.verifier - ERROR - 'ima_sign_verification_keys' keylime_verifier[4785]: Traceback (most...

This would be really great to have. It might also help to "decrease" cloud costs. Could you maybe consider planning it for implementation?

I think that the build on F39 is failing due to some repodata (cache) issue. It is installing old i686 version of tpm2-tss-devel from fedora repo instead of installing it...

You could try editing `packit-ci.fmf` and adding explicit call of `dnf makecache` to https://github.com/mpeters/rust-keylime/blob/spire-apis/packit-ci.fmf#L19 It could fix this problem, though prolong test execution a bit.