-
Notifications
You must be signed in to change notification settings - Fork 20
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
Stucks at "Reading PCR values" #3
Comments
Hello @bypass1 , Would you tell me about your system information? If so, I can help you. Best regards, Seunghun |
Hey Seunghun, Tested systems were: Let me know if you need more information. |
Hi @bypass1 , Thank you for your information. As I know, your systems have TPM 2.0 and should have no problem with the Napper v1.3. Would you test your machine according to the sequence below?
If you do so, I can help you. :) Best regards, Seunghun |
I tested 3 devices again. Fujitsu U728 Dell Latitude 5500 script works well. |
Hi @bypass1 , According to your test results, Fujitsu U728 may not have TPM 2.0. Other systems have TPM 2.0. :) Best regards, Seunghun |
Thanks for your support. Do you know if i can assume that the device isnt vulnerable for this behavior? |
Hi @bypass1 , I'm sorry. I'm not sure that your system has no vulnerability. The result just showed that Linux OS doesn't support your TPM device. For ensuring your system is safe, you should check the history of the BIOS update page and update it with the latest version of BIOS firmware. If you have any further questions, feel free to ask me. :) Best regards, Seunghun |
i created a usb boot stick, confirmed TPM v2.0 is enabled in BIOS and followed the instructions to use your script.
it stucks at "Reading PCR values of TPM......", i waited for 1 hour and tried two different systems.
does it takes longer than this or is it a bug or some other error?
additional infos: i tried the "tpm2_getinfo" executable and it throws an error too:
"Resource Mgr, resMgr, failed to initialization: 0x1. Exiting"
The text was updated successfully, but these errors were encountered: