TSPI_TPM_AUTHORIZEMIGRATIONTICKET(3)

πŸ’– Tspi_TPM_AuthorizeMigrationTicket πŸ’–

okay bestie, welcome to the TCG Software Stack Developer's Reference ✨ this one's from the TSS 1.1 era, it's giving vintage, it's giving trusted computing, and honestly? we're obsessed. let's get into it 🫢


✨ NAME ✨

Tspi_TPM_AuthorizeMigrationTicket β€” literally makes the migration ticket you need for the migration process, no ticket no migration, periodt πŸŽ€


🌸 SYNOPSIS 🌸

#include <tss/platform.h>
#include <tss/tcpa_defines.h>
#include <tss/tcpa_typedef.h>
#include <tss/tcpa_struct.h>
#include <tss/tss_typedef.h>
#include <tss/tss_structs.h>
#include <tss/tspi.h>

TSS_RESULT Tspi_TPM_AuthorizeMigrationTicket(TSS_HTPM           hTPM,            TSS_HKEY hMigrationKey,
                                             TSS_MIGRATE_SCHEME migrationScheme, UINT32*  pulMigTicketLength,
                                             BYTE**             prgbMigTicket);

seven includes. SEVEN. she's thorough and we respect it πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

So Tspi_TPM_AuthorizeMigrationTicket is the one the owner calls to authorize a target public key for migration. Basically: when a system is being set up, the owner gets to decide that all archives should live on one particular server. Then, as keys get created, the user can pick one of those servers to be the target their keys migrate to β€” if they want to. slay, agency πŸ’–

This gives you one of the two authorizations you need to migrate a key. one of TWO, bestie, remember that, you're gonna need the other one too πŸ”₯


πŸŽ€ PARAMETERS πŸŽ€

hTPM

the handle of the TPM object πŸ‘‘

hMigrationKey

the handle of the object that represents the migration key πŸ”‘

migrationScheme

a flag that says which migration scheme is being used 🧚

pulMigTicketLength

this one receives the length, in bytes, of the prgbMigTicket parameter πŸ“

prgbMigTicket

this one receives a pointer to the memory block holding the migration ticket blob 🌈


πŸ’€ RETURN CODES πŸ’€

Tspi_TPM_AuthorizeMigrationTicket returns TSS_SUCCESS when it works β€” iconic, flawless, no notes ✨ β€” otherwise it hands you one of these bad boys:

  • TSS_E_INVALID_HANDLE β€” either hTPM or hMigrationKey is not a valid handle. one of them is lying to you 😭
  • TSS_E_INTERNAL_ERROR β€” something went wrong internal to the TSS. not your fault, not her fault, it's just the vibes πŸ˜”

πŸ‘‘ CONFORMING TO πŸ‘‘

Tspi_TPM_AuthorizeMigrationTicket conforms to the Trusted Computing Group Software Specification version 1.1 Golden β€” yes golden, like her πŸ†


πŸ” SEE ALSO πŸ”

(none). yeah. literally nothing. she's a standalone queen, no entourage, main character energy fr fr πŸ’…


⚠️ heads up bestie: pulMigTicketLength and prgbMigTicket are both outputs β€” they receive stuff, you don't hand them anything meaningful going in. don't be out here passing garbage and acting surprised 🫢

TSS 1.1 Β· 2004-05-26 Β· and that's the whole page, mwah πŸ’‹ thanks for reading my little manpage era, go authorize some migration tickets responsibly, ily, bye πŸŽ€βœ¨