You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-23
Original file line number
Diff line number
Diff line change
@@ -21,8 +21,6 @@ see the [example/](example/) folder for more information.
21
21
22
22
---
23
23
24
-
25
-
26
24
>> this library is not supported by google
27
25
28
26
---
@@ -77,11 +75,8 @@ If you just want to issue JWT's, see
77
75
78
76
### TPM Signer Device management
79
77
80
-
>> **NOTE** there will be a breaking change if you are using this library for TPM based signature after `v0.8.0`. The new structure uses the [tpm-direct](https://github.com/google/go-tpm/releases/tag/v0.9.0) API. If you would rather use the tpm2/legacy branch, please use the signer at [v0.7.2](https://github.com/salrashid123/signer/releases/tag/v0.7.2). While this repo still retain managed and unmanaged handles to the TPM device, its recommended to to manage it externally if you need complex authorization...if its simple authorization like pcr and password or if you need concurrent, non blocking of the TPM device, use library managed handle. For externally manged, just remember to open-sign-close as the device is locking.
78
+
>> **NOTE** there will be a breaking change if you are using this library for TPM based signature after `v0.8.0`. The new structure uses the [tpm-direct](https://github.com/google/go-tpm/releases/tag/v0.9.0) API. If you would rather use the tpm2/legacy branch, please use the signer at [v0.7.2](https://github.com/salrashid123/signer/releases/tag/v0.7.2). Library managed device was removed (it seems tpm resource managers work well enough...I'm clearly on the fence here given the recent commits..)
81
79
82
-
For TPM Signer, there are two modes of operation:
83
-
84
-
* managed externally
85
80
86
81
The TPM device is managed externally outside of the signer. You have to instantiate the TPM device ReadWriteCloser and client.Key outside of the library and pass that in.
87
82
@@ -107,23 +102,6 @@ For TPM Signer, there are two modes of operation:
This is the preferred mode: you just pass the uint32 handle for the key and the path to the tpm device as string and the library opens/closes it as needed.
113
-
114
-
If the device is busy or the TPM is in use during invocation, the operation will fail.
115
-
116
-
```golang
117
-
r, err:= saltpm.NewTPMCrypto(&saltpm.TPM{
118
-
TpmPath: *tpmPath,
119
-
KeyHandle: tpm2.TPMHandle(*handle).HandleValue(),
120
-
PCRs: []uint{},
121
-
AuthPassword: []byte(""),
122
-
})
123
-
124
-
// the tpm is opened and then closed after every sign operation
0 commit comments