Laurent Bigonville

I see this commit: https://sourceforge.net/p/trousers/tpm-tools/ci/8f253fbc61b8afb6a5d341090bba31dada29dffd/ that fixed an other occurrence of this apparently Edit: Is that patch actually correct?

I see this commit: https://sourceforge.net/p/trousers/tpm-tools/ci/8f253fbc61b8afb6a5d341090bba31dada29dffd/ that fixed an other occurrence of this apparently

Any new about this bug? This breaks the build on x32 architecture as the target is x86_64-pc-linux-gnux32 The compiler should already know what to do for the target architecture without this flag

Isn't openssl 1.1 supported now? That should be closed

tpm_nvcommon.c:167:31: warning: comparison of constant ‘124’ with boolean expression is always false [-Wbool-compare]

Actually tpm_resetdalock is not the only one, tpm_unsealdata also doesn't list the -u option

Please indicate in the manpage that tpm_restrictpubek is permanant

tpm_resetdalock doesn't list -u option