Go Cryptography: Repository Root
This repository holds supplementary Go cryptography packages.
Search SSH
Ssh - Search
share.google/TJUdgYlA1I35aik…
The ssh package has 50 imports.
Here's the hyperlink to all the Go Cryptography packages implemented in 50 different open source modules and libraries.
ssh package imports -
golang.org/x/crypto/ssh - Go Packages
share.google/yCNZxKSEHAopCkT…
◽Teleport Workload Identity
Teleport Workload Identity securely issues short-lived cryptographic identities to workloads. It is a flexible foundation for workload identity across your infrastructure, creating a uniform way for your workloads to authenticate regardless of where they are running.
Teleport Workload Identity is compatible with the open-source Secure Production Identity Framework For Everyone (SPIFFE) standard.
goteleport.com/docs/enroll-r… This enables interoperability between workload identity implementations and also provides a wealth of off-the-shelf tools and SDKs to simplify integration with your workloads.
goteleport.com/docs/enroll-r…
Issue and govern identities for automated systems using Teleport Machine Identity.
MachineID
Teleport Machine ID enables machines, such as CI/CD workflows, to securely authenticate with your Teleport cluster in order to connect to resources and configure the cluster itself. This is sometimes referred to as machine-to-machine access.
goteleport.com/docs/enroll-r…
🔸SPIFFE (Secure Production Identity Framework For Everyone)
A set of standards for securely identifying workloads.
SPIFFE sets out:
A format for uniquely specifying an identity called SPIFFE ID.
Standards for encoding the SPIFFE ID into verifiable documents which are called SVIDs (SPIFFE Verifiable Identity Document), and which come in a JWT and X.509 format.
Processes that workloads should use to validate a received SVID.
A set of APIs that workloads can use to request SVIDS, the Workload API.
🔸Secure Verifiable Identity Documents (SVIDs)
The SPIFFE ID may be a unique identifier for a workload, but provides no way for a workload to verifiably prove its identity. This is where the Secure Verifiable Identity Documents (SVIDs) come in.
The SVID is a document that encodes the SPIFFE ID and a cryptographic proof which allows the SVID to be verified as issued by a trusted authority.
SPIFFE sets out two formats for SVIDs:
X.509-SVID: These are X.509 certificates that include the SPIFFE ID encoded in the URI SAN field. This certificate is then signed by a trusted authority within the trust domain.
JWT-SVID: These are JWT tokens that include the SPIFFE ID as the sub claim. These are signed by a trusted authority within the trust domain.
The data needed by a workload to verify a SVID is known as the trust bundle. This is a set of certificates belonging to the trusted authorities within the trust domain.
🔸SPIFFE Specification
The official SPIFFE specification. Useful for understanding the SPIFFE ID and SVID formats.
github.com/spiffe/spiffe/blo…
🔸SPIFFE Standards docs
github.com/spiffe/spiffe/tre…
🔸The SPIFFE Workload API
Portable and interoperable cryptographic identity for networked workloads is perhaps the core use case for SPIFFE. In order to wholly address this requirement, the community must converge upon a standardized way to retrieve, validate, and interact with SPIFFE identities. This specification outlines the API signatures and client/server behavior required in order to support SPIFFE-based authentication systems.
github.com/spiffe/spiffe/blo…