Andrew Harding
Andrew Harding
Some specs have requirements on certain choices (e.g. extended key usage bits on X509-SVID) without the accompanying justification. This can cause confusion and extra work as readers seek out answers...
### Documentation - [X] I've gone though the [API reference](https://docs.aws.amazon.com/sdk-for-go/v2/api/) - [X] I've checked [AWS Forums](https://forums.aws.amazon.com) and [StackOverflow](https://stackoverflow.com/questions/tagged/aws-sdk-go) for answers - [X] I've searched for [previous similar issues](https://github.com/aws/aws-sdk-go-v2/issues) and didn't...
When cgo picks up OpenSSL 3.0 (for example via brew on macOS), compilation outputs quite a few deprecation warnings similar to the following: ```In file included from include.c:172: /redacted/go/pkg/mod/github.com/google/[email protected]/simulator/ms-tpm-20-ref/TPMCmd/tpm/src/crypt/ossl/TpmToOsslMath.c:600:9: warning:...
The Identity Management Using SPIRE for Kubeedge demo places the spiffe-helper between Ghostunnel and SPIRE agent in order to allow Ghostunnel to consume resources off of the SPIFFE Workload API....
There have been some requests to allow X509-SVID or JWT-SVID field customization. One way in which this might be achieved is by creating a new plugin type that would get...
As pointed out in #3110, SPIRE is not RFC compliant in its issuance of X509-SVIDs. The requirement of the RFC is that the Subject DN be unique to each entity,...
#3272 deprecated the (only) node resolver plugins and interface. This issue tracks removal of the plugins and interface in SPIRE 1.5.0.
SPIRE has assumed that node attestors would produce agent IDs that conform to the following convention: ``` spiffe:///spire/agent// ``` (e.g. `spiffe://example.org/spire/agent/join_token/21B6D625-CCF3-49E1-8E7C-812B3F55B3CB`) Although this convention is not required for agent authorization...
This issue tracks a discussion on how to provide improved support for workloads running in ECS or similar environments. Due to the auto-scaling nature of these types of environments, current...
Encountered the following test failure running the race tests in CI/CD on GH: ``` 2022/07/01 18:42:52 http: TLS handshake error from 127.0.0.1:46624: tls: client didn't provide a certificate 2022/07/01 18:42:52...