* add PolicyAuthValue

* add nil authoption test

* add EncryptDecrypt2 support

Signed-off-by: sal rashid <salrashid123@gmail.com>

* simplify tests

Signed-off-by: sal rashid <salrashid123@gmail.com>

---------

Signed-off-by: sal rashid <salrashid123@gmail.com>

* add TPM2_PolicyDuplicationSelect

Signed-off-by: sal rashid <salrashid123@gmail.com>

* modify name; consolidate calls

Signed-off-by: sal rashid <salrashid123@gmail.com>

* simplify tests

Signed-off-by: sal rashid <salrashid123@gmail.com>

---------

Signed-off-by: sal rashid <salrashid123@gmail.com>

…ect (#366)

Add TPMFW (firmware) handles to go_tpm from updated TCG specs at https://trustedcomputinggroup.org/wp-content/uploads/TPM-2.0-1.83-Part-2-Structures.pdf#page83 and add FirmwareLimited attribute to TPMAObject and allow to the validation to accept keys with and without the bit set

This change adds a missing doc comment for EncryptDecrypt2, and adds the
missing `nullable` tag onto HmacStart's hash algorithm. The hash
algorithm can be TPM_ALG_NULL (see TPM Spec Part 3).

* Create individual packages for Windows and Linux TPM transport

#364 called to attention some
long-standing technical debt around TPM transport. In particular, the
stack looks like:

(Linux or Windows) `OpenTPM` function
calls the legacy `OpenTPM` function
calls the tpmutil `OpenTPM` function

At the bottom of the stack, tpmutil does some runtime introspection to
see what type of TPM it wants to open (e.g., on Linux, the device could
be either a device file or a socket). This runtime support is
convenient, but also breaks dead-code elimination (for example, tinygo
will fail to compile the UDS support code, and users have no way of
leaving that out without patches).

In principle, we've found within Google that "open my TPM" should be as
un-smart as possible, to avoid awkward edge cases (for example, what
happens if the logic finds two different TPMs on the system; which
should it prefer; should it invisibly succeed and surprise the user?).
Instead, the preferred pattern is to require the user to explicitly say
which TPM they are trying to open.

This change introduces 3 packages as a replacement for
`transport.OpenTPM` (which this change marks as now Deprecated):

`transport/linuxtpm.Open(path)` opens Linux device TPMs (e.g., /dev/tpm0 or
/dev/tpmrm0)
`transport/linuxudstpm.Open(path)` opens Linux Unix Domain Socket TPMs
`transport/windowstpm.Open()` opens the TPM from TBS.dll

Intentionally, the now-deprecated `transport.OpenTPM` is not touched.
This would create an import cycle.

* Add small tests for each of the openers

* fix lint

* fix linuxudstpm and test

* fix the test in the case that the UDS simulator is not running

* remove extraneous test for windows

* Fix KnownName, add Sequence Handle name handling

* Fix RSADecrypt Name in test

* Relax HmacStart.Handle type

* Add additional comment context to change