Re: [Qemu-discuss] Trustedgrub2 reports No TPM found

2017-05-05 Thread Stefan Berger
I would use the following configure lines. You may want to watch out so you don't have two versions of the library on your system, though: libtpms: ./configure --prefix=/usr --with-tpm2 --with-openssl ; make ; make check ; sudo make install swtpm: ./configure --prefix=/usr --with-op

Re: [Qemu-discuss] Trustedgrub2 reports No TPM found

2017-05-10 Thread Stefan Berger
files/?source=navbar Regards, Stefan - Original message - From: anshul makkar To: Stefan Berger Cc: Subject: Re: Trustedgrub2 reports No TPM found Date: Wed, May 10, 2017 4:41 AM Hi Stefan, Thanks.. " swtpm: ./configure --p

Re: [Qemu-discuss] Trustedgrub2 reports No TPM found

2017-05-10 Thread Stefan Berger
IBM TPM tools you should do the following: export TPM_INTERFACE_TYPE=dev pcrread -ha 1 That show something like this: count 1 digest length 32 00 00 00 00 ... Regards, Stefan - Original message - From: anshul makkar To: Stefan Berger Cc

Re: Bitlocker-tripping hardware change with 5.2.0?

2020-12-19 Thread Stefan Berger
On 12/17/20 10:54 AM, Marc-André Lureau wrote: Hi On Wed, Dec 16, 2020 at 11:45 PM Michael Weiser ... Could it be as easy as booting a recovery linux distro and comparing the outputs of dmidecode or somesuch? I am afraid it's not so easy.  We should probably consider new tests

Re: Bitlocker-tripping hardware change with 5.2.0?

2020-12-20 Thread Stefan Berger
On 12/20/20 8:25 AM, Michael Weiser wrote: Hi Stefan, On Sat, Dec 19, 2020 at 11:02:29PM -0500, Stefan Berger wrote: The whole purpose of measured/trusted boot is to reflect some known measurement values of a known BIOS in the TPM PCRs. Unfortunately this bites with sealing to those values