Automatically provision and manage TLS certificates in Kubernetes
-
Updated
Jul 4, 2024 - Go
TLS (Transport Layer Security) is a cryptographic protocol designed to provide communications security over a computer network. The protocol is widely used in applications such as email, instant messaging, and voice over IP, but its use in securing HTTPS remains the most publicly visible.
The TLS protocol aims primarily to provide security, including privacy (confidentiality), integrity, and authenticity through the use of cryptography, such as the use of certificates, between two or more communicating computer applications. It runs in the presentation layer and is itself composed of two layers: the TLS record and the TLS handshake protocols.
TLS builds on the now-deprecated SSL (Secure Sockets Layer) specifications (1994, 1995, 1996) developed by Netscape Communications for adding the HTTPS protocol to their Navigator web browser.
Automatically provision and manage TLS certificates in Kubernetes
trust-manager is an operator for distributing trust bundles across a Kubernetes cluster.
Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
An ACME-based certificate authority, written in Go.
A simple TLS proxy, Reverse proxy, and Web server that uses Let's Encrypt automatically.
Let's Encrypt/ACME client and library written in Go
A private Certificate Authority for internal (lab) use, based on the open source ACME Automated Certificate Management Environment implementation from Let's Encrypt (tm).
An easy-to-use HTTP client 100% in Go to spoof TLS/JA3 and HTTP2 fingerprint
🧰 A zero trust swiss army knife for working with X509, OAuth, JWT, OATH OTP, etc.