On 02/08/15 11:32, cprise wrote:
> A problem here is that the Qubes HCL script does not check for TPM
> presence, so the people sending HCL reports who do not care about AEM
> (or don't yet use AEM at the time they report) create an entry in the
> HCL that leaves the TPM column blank.
>
> I've suggested adding TPM support to the HCL script to help fill the
> voids and at least give readers a preliminary indication that a TPM is
> accessible by Qubes in a given system.
We have several blocking point about this feature:
- all the mentioned features like vt-d, vt-x, TPM are depends on the
BIOS in several ways. Even in the best scenarios the user can simply
leave disabled it in the BIOS.
In this case no script will tell why do get a "not supported" results.
- all the HCL reports are completely depends on the USER who reported it.
Even the script says all features are working and enabled we really
don't know if it is really working without any glitches or not.
So here we all depending on user reports.
- lots of users are not willing to provide any info about their devices
for several reasons.
- My current device is a corporate one and our corp using a mindlessly
stupid security policy. Because of that I'm not even able switch any
feature in BIOS on my own - so really not able to test anything about
TPM. (And I guess I'm not the only one in this boat)
But let me qo back to the TPM detection:
There was another thread about this and I just asked to get some
positive and some negative results about TPM status.
I only got one (1) single positive results. From that single result I'm
not able to write a TPM detection script - sorry.
So about to get better HCL info in general:
If any notebook provider would give me devices to test Qubes
compatibility I would love to do check them and post the results.
Feel free to contact me about this :)
--
Zrubi