TSPI_CHANGEAUTH(3)

πŸ’– Tspi_Change_Auth(3) πŸ’–

okay bestie, welcome to the TCG Software Stack Developer's Reference ✨ this one's a lil glow-up page for your objects, fr fr.


🌸 NAME 🌸

Tspi_ChangeAuth β€” change the authorization data of an entity.

like… the secret password thing? yeah. we're swapping it. πŸ’…


✨ 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_ChangeAuth(TSS_HOBJECT hObjectToChange, TSS_HOBJECT hParentObject,
                           TSS_HPOLICY hNewPolicy );

look at all those includes. she's prepared. she's got the whole TSS closet unpacked πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

so Tspi_ChangeAuth changes the authorization data (that's the secret, the lil password vibe) of an entity β€” and yes, an entity is an object here, keep up bestie 😌 β€” and then it assigns the object to the policy object.

and the tea? all classes using secrets provide this method for changing their authorization data. every single one. it's giving universal. it's giving main character energy for every secret-holding class out there πŸ‘‘


πŸ’œ PARAMETERS πŸ’œ

hObjectToChange

handle of the object you wanna change authorization for. the glow-up target 🫢

hParentObject

handle of the parent object β€” the one wrapping the object addressed by hObjectToChange. so like, your object has a parent. we respect that. we go through the parent. πŸ’…

hNewPolicy

handle of the policy object that's providing the new authorization data. this is the new secret. the new era. the rebrand. ✨


πŸ”₯ RETURN CODES πŸ”₯

Tspi_ChangeAuth returns TSS_SUCCESS on success β€” slay, we love a win πŸ’– β€” otherwise one of these lil guys comes back at you:

  • TSS_E_INVALID_HANDLE β€” either hObjectToChange, or hParentObject are not a valid handle. πŸ’€
  • TSS_E_INTERNAL_ERROR β€” an error occurred internal to the TSS. not us, it's internal. it's their business. πŸ™ˆ

🌈 CONFORMING TO 🌈

Tspi_ChangeAuth conforms to the Trusted Computing Group Software Specification version 1.1 Golden ⭐ yes ma'am, certified, spec-compliant, iconic.


πŸŽ€ SEE ALSO πŸŽ€


okay and for the sign-off, since you asked so nicely: this page is from TSS 1.1, dated 2004-05-26 β€” yeah she's vintage, but she still ate πŸ’…βœ¨ bye bestie, go change some auth data responsibly πŸ¦‹