TLS certificate
A signed digital document that proves a server really owns a domain name and holds the key used to start encrypted TLS connections.
In more detail
During the TLS handshake the server sends its certificate, and the client checks that a trusted certificate authority signed it and that it matches the host name. If the check fails the connection is refused or, in a browser, a warning is shown.
Examples
COPY --from=build /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/Go in a scratch image: COPY the CA bundle from the build stageIt records a subject, the names it is valid for, an issuer, validity dates and the issuer's signature. Clients check the chain up to a trusted root, the dates and that the requested hostname is listed. A wrong name and an expired certificate need different fixes, so read the details before replacing anything.host=example subj=example iss=inter chain=ok names the requested host, subject, issuer and chain result.Related terms
- TLS — The encryption that protects data travelling over a network, the S in HTTPS.
- session key — A temporary secret key that the browser and server agree on during the TLS handshake and use to encrypt one connection.
- host name — The name a computer or container calls itself on a network.
- cert-manager — A Kubernetes add-on that requests TLS certificates, stores them as secrets and renews them before they expire.
- Let’s Encrypt — A free, automated certificate authority that issues the TLS certificates for a large share of websites.
- HTTP — The protocol web browsers and web servers use to send requests and responses.
- scratch — Docker's special empty base image, with no files at all, used to ship a single static binary and nothing else.
- minimal base image — A base image with as little inside as possible, such as Alpine, a slim variant or a distroless image, to shrink size and attack surface.
- certificate chain — The sequence of certificates from a server's certificate, through one or more intermediate certificates, up to a trusted root.
- certificate authority — A trusted party that signs certificates, so anyone who trusts it can trust the certificates it issued.
- hostname verification — The client's check that the name it asked to connect to appears in the server certificate.
- certificate expiry — The end of a certificate's validity period, after which clients refuse it even if everything else is correct.
- public key — The shareable half of a key pair, used by others to verify your signatures or encrypt data only you can read.
- public key infrastructure — The system of certificate authorities, certificates and trust rules that lets a client check a server's public key really belongs to that server.
- Subject Alternative Name — The certificate field that lists every host name, and sometimes IP address, the certificate is valid for.
- ACME — The protocol certificate authorities such as Let's Encrypt use to issue and renew TLS certificates automatically.
Taught in
- Twenty Minutes Down At Lunchtime: App Service Plans And Slots — Microsoft Azure Administrator (AZ-104) Exam Prep
- Ten Workloads, One Week: The Compute Decision Drill — Microsoft Azure Administrator (AZ-104) Exam Prep
- Seventy-Two Percent, Now What? The Full Mock And Your Review Plan — Microsoft Azure Administrator (AZ-104) Exam Prep
- Six Seconds, Every Secret — Certified Kubernetes Security Specialist (CKS) Exam Prep
- The Metadata Endpoint And The Kubelet's Front Door — Certified Kubernetes Security Specialist (CKS) Exam Prep
- kube-bench: Ten Failures On A Fresh Cluster — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Ingress TLS: When The Padlock Lies — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Verify Binaries: A Hash With No Name — Certified Kubernetes Security Specialist (CKS) Exam Prep
- ServiceAccounts: Take Back The Key — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Anonymous Access: The Fix That Kills The API Server — Certified Kubernetes Security Specialist (CKS) Exam Prep
- The Host Footprint: Six Doors On A Worker — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Encryption At Rest: What etcd Really Holds — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Encrypting Pod-to-Pod Traffic: mTLS With Istio And Cilium — Certified Kubernetes Security Specialist (CKS) Exam Prep
- SBOMs: Knowing What You Ship — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Allowed Registries: Admission That Refuses Images — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Signing And Verifying Images With Cosign — Certified Kubernetes Security Specialist (CKS) Exam Prep
- How Browsers Work: Navigation, DNS, TCP, TLS And Request Timing — Frontend Architecture & Web Platform
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- Shipping in Scratch and Distroless Images — Concurrent Systems Programming with Go
- One Leaked Kubeconfig: How Far Does It Go? — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Seven Findings, Two Owners: The 4Cs And Shared Responsibility — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Eleven Months Of Yes: The API Server — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Open To Every Interface: Controller Manager And Scheduler — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Copied From A Blog Post: The Kubelet — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- A Copy Of The Backup: etcd — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Port 30080 On Every Node: kube-proxy, Networking And Clients — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Component Sprint: The Reference Build — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Created, But Never Running: Pod Security Admission — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- There Is No Users Table: Authentication — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Encoded Is Not Hidden: Secrets — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Fundamentals Sprint: Four Findings, Eight Questions — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Draw The Boundaries: Trust And Data Flow — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- One Pod Away: Network Attackers And Sensitive Data — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Who Built This Image? Supply Chain And Registries — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Four Alerts, One Incident: Observability And The Mesh — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- A Cluster's First Birthday: PKI And Connectivity — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Platform Sprint: Evidence, Order, Proof — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Audit Day: Final Review — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Control Plane: etcd, API Server, Scheduler, Controllers — Kubernetes: Production-Grade Container Orchestration
- Bootstrap A Local Cluster And Check Your Context — Kubernetes: Production-Grade Container Orchestration
- Ingress: Controllers, Hosts, Paths And TLS — Kubernetes: Production-Grade Container Orchestration
- NetworkPolicy And The Consul Service Mesh Boundary — Kubernetes: Production-Grade Container Orchestration
- Authentication, ServiceAccounts And Short Lived Tokens — Kubernetes: Production-Grade Container Orchestration
- kubeadm, High Availability And Cluster Lifecycle — Kubernetes: Production-Grade Container Orchestration
- Drain, Upgrade, Version Skew And Certificate Maintenance — Kubernetes: Production-Grade Container Orchestration
- etcd Snapshots And A Tested Restore — Kubernetes: Production-Grade Container Orchestration
- What HTTPS Adds, And What It Does Not — Linux Fundamentals & Systems Administration
- Certificates, Chains And What A Handshake Proves — Linux Fundamentals & Systems Administration
- TLS & HTTPS Encryption: Certificates & SNI Contexts — Node.js Internals & Backend Services
- Secure Defaults — Application Security & Threat Modeling for Engineers
- TLS And The Handshake — Application Security & Threat Modeling for Engineers
- Two Managers Down: The Night The Swarm Froze — Docker Certified Associate (DCA) Exam Prep
- Our Own Registry: Deploy, Push, Pull, Search And Delete — Docker Certified Associate (DCA) Exam Prep
- One Comma, No Engine: Installing And Configuring Docker Engine — Docker Certified Associate (DCA) Exam Prep
- Forty Gigabytes Of One Log: Logging Drivers And Their Options — Docker Certified Associate (DCA) Exam Prep
- Port 2375, Open To The Office: Engine TLS And Registry Certificates — Docker Certified Associate (DCA) Exam Prep
- Two Of Everything: Deploying, Sizing And Backing Up UCP And DTR — Docker Certified Associate (DCA) Exam Prep
- Installation Sprint: Eight Configuration Calls — Docker Certified Associate (DCA) Exam Prep
- Any Node, Any Task: Overlay Networks, The Routing Mesh And Layer 7 — Docker Certified Associate (DCA) Exam Prep
References
- MDN: Transport Layer Security
- RFC 5280: Internet X.509 certificate profile
- Kubernetes: TLS Secrets
- Let’s Encrypt: How it works
- Package crypto/x509
- OWASP Transport Layer Security Cheat Sheet
- OpenSSL docs: openssl-x509