nit: These symbols don't have a name in the spec. I like your suggestions except for the extra S: could you name them TPMIDHSavedTransient, TPMIDHSavedSequence, etc.

Updated in f3f6077

Are you sure it's right to add TPMHTTransient here? A transient object's name is not just the big-endian byte array of its handle, unlike with PCR, HMAC and Policy sessions, and Permanent entities.

(Thank you for the cleanup though, putting the actual symbols here!)

Thanks for calling this out, I mis-interpreted Part 2 Structures section 14.6.2 savedHandle.

Based on the table from Part 1 Architecture section 16 Table 3, I changed the handling in 0d43555 to address the case of a sequence object and to allow for Name computation of Transient and Persistent Objects in future implementations.

I first thought of changing the AuthHandle{} KnownName() method because passing in an empty AuthHandle.Name¹ would default to AuthHandle.Handle.KnownName() being called, which will always be nil because the Name associated with a sequenceHandle is an empty buffer¹. The nil Name value would then error in cmdNames.

Rather than modify the AuthHandle struct method I opted to extend the Name computation since it is defined for both Transient and Persistent Objects in Part Architecture section 16 Table 3.

Concerns or suggestions?

¹ Part 1: Architecture, section 32.4.5