Dear,

I'm handling a TPM with Exynos5422, and Debian Jessie as an OS.
TPM is connected via I2C with SoC.
 - Kernel ver: 3.10.96
 - Debian Jessie 8.1
 - trousers: 0.3.13-4
 - tpm-tools: 1.3.8-2

After start TrouSers, tpm_version command shows as follow;
Restarting trousers (via systemctl): trousers.service.
  TPM 1.2 Version Info:
  Chip Version:        1.2.133.32
  Spec Level:          2
  Errata Revision:     3
  TPM Vendor ID:       IFX
  Vendor Specific data: 85200050 0074706d 3438ffff ff
  TPM Version:         01010000
  Manufacturer Info:   49465800

However, when I try to takeownership, it returns an error as follow;
and setenable as well.

root@odroid:/home/odroid# tpm_takeownership
Enter owner password:
Confirm password:
Enter SRK password:
Confirm password:
Tspi_TPM_TakeOwnership failed: 0x00000007 - layer=tpm, code=0007 (7), TPM
is disabled

root@odroid:/home/odroid# tpm_clear -f
Tspi_TPM_ClearOwner failed: 0x00000007 - layer=tpm, code=0007 (7), TPM is
disabled

root@odroid:/home/odroid# tpm_setenable -e
Enter owner password:
Tspi_TPM_SetStatus failed: 0x00000001 - layer=tpm, code=0001 (1),
Authentication failed

root@odroid:/home/odroid# tpm_setenable -e
Enter owner password:
Tspi_TPM_SetStatus failed: 0x00000803 - layer=tpm, code=0803 (2051), TPM is
defending against dictionary attacks and is in some time-out period
-------------------------

I cannot clear TPM nor get ownership for further job.
Any idea would be appreciated.

Thanks
mipsan
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
TrouSerS-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/trousers-users

Reply via email to