Research: Analysis of Trusted Platform Module chips

This guide is already out of date. Please use the version on page

The goal of the research is to get a better understanding of the Trusted Platform Modules ecosystem. Such information is vital for the designers and developers using this technology, allowing then to answer questions like: What fraction of devices has TPM chip? Which cryptographic algorithms are widely supported? What is the overhead of computing a digital signature?

The research consist of two primary steps:

  1. Collection of raw data about TPM chips deployed in real-world devices like notebooks, desktops, and servers (the part we are asking you for kind help).
  2. Analysis of the data collected to provide insight into the TPM ecosystem (done by us, resulting in a summary of the most important findings, scientific paper, and research dataset available for replicability and further research).

The data collection consists of 3 principal steps:

  1. Preparation of bootable USB drive (20 minutes to download image and 10 minutes to setup)
  2. TPM data collection (1-3 hours) using live image
  3. Send collected data (anonymous upload, email)
  • (step 2., and 3., can be repeated for multiple computers, no need to create USB drive again)

1. Preparation of bootable USB drive

Duration: Preparation of bootable device will take approximately 20 minutes to download image and 10 minutes to setup.

  1. Prepare an empty USB drive with at least 4GB size (IMPORTANT: all content will be erased)
  2. Download live USB image: algtest-usb-disk.img and save to disk (e.g., folder C:\TPM\)
  3. Download and install Balena Etcher (Windows, Linux, Mac) to create bootable USB drive. (Alternatively, you may use Rufus instead (Windows only)).
  4. Run Balena Etcher, click Select image and browse for previously downloaded algtest-usb-disk.img on your disk
  5. Insert empty USB drive, click Select target and pick the USB disk
    • (double-check that displayed drive is your intended USB drive – check the label, check size)
  6. Click Flash! and wait approximately 5 minutes until flashing is completed.

Click to enlarge the image.
Click to enlarge the image.

2. Data collection

Duration: Running Fedora-based system from the bootable device and data collection will take approximately 2-3 hours.

  • Place your computer to steady location (on the desk) and plug in power cable.
  • Insert installed USB drive from step 1 into the computer and restart your machine.
  • If prompted, select boot from USB device instead of standard disk. Select Start Fedora-algtest-Live 32 boot option.

Click to enlarge the image.

  • Wait until Fedora-based TPM testing system is booted. Read the summary of the data we are collecting.

Click to enlarge the image.

  • Press the Start button
    • Check that test started and is running (Log window contains 'XX:YY:ZZ Collecting basic TPM info…').

Click to enlarge the image.

  • Wait for 2–3 hours until the test is finished (100% Test progess).
    • IMPORTANT: If test will not finish even after 5 hours and no visible progress is seen, please press the Stop button and continue to upload the partial results.
  • Press the Shutdown PC button; wait until your machine is stopped. Unplug the USB drive.
  • Restart your computer to your standard environment

3. Submit collected data

  1. Make sure the USB drive is unplugged.
  2. Start into your standard environment (e.g., Windows, Linux).
  3. Plug the USB drive, new drive with label algtest_res is mounted (e.g., 'E:\').
  4. Locate file(s) with a file name in the form of
  5. Visit page;vybos_vzorek=4085 and follow instructions how to upload the file (no authentication required, just drop the files). Alternatively, send email to Petr Svenda with file attached.

Upload collected data here  or send data by email to <>.

Click to enlarge the image.

You are now all good and helped research – Thank you a LOT!


Issue: Solutions below does not solve the problem

Solution: If you have any issue which solutions below will not help with, please notify us at

Issue: The bootable image cannot be downloaded

Solution: Download from the secondary backup location. Please notify us at

Issue: The live Fedora system will not start to boot

Solution: Go to BIOS (press F1, F8, F12, Enter or special button depending on your computer), select alternative boot device (USB you flashed) and continue

Issue: The live Fedora system will stop with error during boot

Solution: Try to change USB slot used to insert bootable USB disk, try to put device into stable position to prevent interruption of communication to USB disk

Issue: The TPM data collection will start, but finish very quickly (less than 10 seconds) with error 'Cannot collect TPM 2.0 info. Your TPM may probably be disabled in BIOS or you do not have a TPM 2.0.'

Solution 1: Restart your computer, enter BIOS (press F1, F8, F12, Enter or special button right), enable option named as 'TPM chip', 'Security chip' or similar. Then try to boot from USB again.

Solution 2: Try to update your BIOS if possible (older BIOSes are known to have incompatibility with some TPM chips under Linux). Then restart and boot from USB again.

Please submit the results even if the error persists.

Issue: I want to see the source code and build live image myself

Solution: You are more than welcome, please visit for live image builder repository and (collection tool itself).

Research details

 Experiment: Analysis of Trusted Platform Modules

 Primary contact: doc. Petr Svenda <>

 Research institute: CRoCS laboratory, Masaryk University and Red Hat Czech

 Collected data:

We do not collect any personal data. We collect only the TPM chip metadata, performance measurements and temporary cryptographic keys generated by TPM chip and product name of your device (e.g., Lenovo ThinkBook 15). We plan to release the data collected later as an open research dataset.

Data we collect:

  • Device vendor, type (e.g., Lenovo ThinkBook 15) and BIOS version.
  • TPM vendor, firmware version (e.g., Intel 401.1.0.0) and TPM version-related information.
  • TPM metadata (TPM_PT_xxx properties like TPM_PT_REVISION, TPM_PT_MANUFACTURER or TPM_PT_PCR_COUNT – see file Quicktest_properties-fixed.txt and Quicktest_properties-variable.txt for full list).
  • Algorithms and commands supported by TPM (TPMA_ALGORITHM and TPMA_CC properties, see Quicktest_algorithms.txt and Quicktest_commands.txt for full list).
  • Performance measurements for various cryptographic algorithms (see Perf_xxx.csv files).
  • Freshly generated, transient keys for ECC and RSA (see Keygen_ECC_xxx.csv and Keygen_RSA_xxx.csv).
  • Note: All mentioned files are stored inside the file.

Data we do NOT collect:

  • Personal information about the user of the computer analyzed.
  • Endorsement key.
  • Attestation key(s).
  • User-specific content of the non-volatile TPM memory (NVRAM).

Data retention:

  • We plan to release the data collected as open research dataset to enable wider research cooperation.
  • The data collected will be first analyzed by CRoCS research team for the purpose of analysis current TPM chip ecosystem. We plan to release the data collected together with the research findings.