spiffe/go-spiffe

GitHub: spiffe/go-spiffe

Stars: 197 | Forks: 85

# go-spiffe (v2) This library is a convenient Go library for working with [SPIFFE](https://spiffe.io/). It leverages the [SPIFFE Workload API](https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md), providing high level functionality that includes: ## Documentation See the [Go Package](https://pkg.go.dev/github.com/spiffe/go-spiffe/v2) documentation. ## Quick Start Prerequisites: 1. Running [SPIRE](https://spiffe.io/spire/) or another SPIFFE Workload API implementation. 2. `SPIFFE_ENDPOINT_SOCKET` environment variable set to address of the Workload API (e.g. `unix:///tmp/agent.sock`). Alternatively the socket address can be provided programatically. To create an mTLS server: listener, err := spiffetls.Listen(ctx, "tcp", "127.0.0.1:8443", tlsconfig.AuthorizeAny()) To dial an mTLS server: conn, err := spiffetls.Dial(ctx, "tcp", "127.0.0.1:8443", tlsconfig.AuthorizeAny()) The client and server obtain [X509-SVIDs](https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md) and X.509 bundles from the [SPIFFE Workload API](https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md). The X509-SVIDs are presented by each peer and authenticated against the X.509 bundles. Both sides continue to be updated with X509-SVIDs and X.509 bundles streamed from the Workload API (e.g. secret rotation). ## Examples The [examples](./examples) directory contains rich examples for a variety of circumstances. ## Supported Go Versions This library tracks the minimum officially supported Go version (i.e. N-1). The only exception to this policy will be in response to a security issue affecting a dependency that forces a premature upgrade. This action is expected to be rare, will not be taken lightly, and not until reasonable efforts to mitigate the security issue while maintaining this policy are pursued. ## Reporting Security Vulnerabilities If you've found a vulnerability or a potential vulnerability in go-spiffe, please let us know at . We'll send a confirmation email to acknowledge your report, and we'll send an additional email when we've identified the issue positively or negatively.
标签:EVTX分析