<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lets-Encrypt on johanneskueber.com</title><link>https://johanneskueber.com/tags/lets-encrypt/</link><description>Recent content in Lets-Encrypt on johanneskueber.com</description><generator>Hugo</generator><language>en_US</language><lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://johanneskueber.com/tags/lets-encrypt/index.xml" rel="self" type="application/rss+xml"/><item><title>Envoy Gateway Configuration to Reach SSL Labs A+</title><link>https://johanneskueber.com/posts/2026-05-14-envoy-gateway-ssllabs-a-plus/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://johanneskueber.com/posts/2026-05-14-envoy-gateway-ssllabs-a-plus/</guid><description>&lt;p&gt;This article documents the Envoy Gateway configuration required to achieve an A+ rating on Qualys SSL Labs, with the rationale for each setting.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="1-tls-security-background"&gt;1. TLS security background&lt;/h2&gt;
&lt;p&gt;Before any application data flows over &lt;code&gt;https://&lt;/code&gt;, the TLS session completes two steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Authentication.&lt;/strong&gt; The server presents an X.509 certificate signed by a trusted Certificate Authority.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Key agreement and encryption.&lt;/strong&gt; Client and server negotiate a session key via a cipher suite (key exchange, signature, bulk cipher, MAC) and encrypt the channel.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Weaknesses in this chain enable specific attack classes:&lt;/p&gt;</description></item></channel></rss>