TPMLIB_ValidateState(3)

okay so bestie, welcome to TPMLIB_ValidateState(3) — that's the page title, and it lives in the libtpms manual 💅 buckle up, because this one is literally a vibe check for TPM state blobs 🫶

✨ NAME ✨

TPMLIB_ValidateState — validate the state blobs of the TPM 🎀

💖 LIBRARY 💖

TPM library (libtpms, -ltpms) ✨

🦋 SYNOPSIS 🦋

#include <libtpms/tpm_library.h>

uint32_t TPMLIB_ValidateState(TPMLIB_StateType st,
                              unsigned int flags);

💅 DESCRIPTION 💅

The TPMLIB_ValidateState() function is your go-to for validating the state blobs that the TPM would read upon TPMLIB_MainInit() or once the TPM_Startup command has been sent to it. no cap 💖

This function is highkey useful for TPM state migration between possibly different version of libtpms. Here the target libtpms needs to be able to determine whether it can support the version of blobs that were migrated, and if this is not the case, the caller can refuse the migration. periodt 👑

The tpmlib_state parameter can be a logical 'or' of one or multiple of the following: TPMLIB_STATE_PERMANENT, TPMLIB_STATE_VOLATILE, or TPMLIB_STATE_SAVE_STATE. The flags parameter is currently not used and should be set to 0. 🌸

The first state blob that should be loaded is the permanent state, since for example the volatile state requires it to be available for validation. 🧚

This function should be called before TPMLIB_MainInit() is invoked. important bestie, don't skip this step 💀💖

🌈 SEE ALSO 🌈

TPMLIB_MainInit(3), TPMLIB_Terminate(3) ⭐

---

okay that's the whole page, bestie 🫶 the footer's source/version is libtpms, it's dated 2026-01-02, and the page name is TPMLIB_ValidateState(3) — slay, you're all caught up 💅💖