<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
      <title>Alek&#x27;s Blog - SNI</title>
      <link>https://blog.none.at</link>
      <description>Production notes on Kubernetes, OpenShift, and OVHcloud: observability, log archiving, service mesh, LLM inference, and digital sovereignty.</description>
      <generator>Zola</generator>
      <language>en</language>
      <atom:link href="https://blog.none.at/tags/sni/rss.xml" rel="self" type="application/rss+xml"/>
      <lastBuildDate>Mon, 16 Mar 2026 00:00:00 +0000</lastBuildDate>
      <item>
          <title>tls-proxy-tunnel: Transparent TLS Tunnelling Through Corporate HTTP Proxies</title>
          <pubDate>Tue, 02 Jul 2024 00:00:00 +0000</pubDate>
          <author>aleks</author>
          <link>https://blog.none.at/blog/2024/2024-07-02-tls-proxy-tunnel/</link>
          <guid>https://blog.none.at/blog/2024/2024-07-02-tls-proxy-tunnel/</guid>
          <description xml:base="https://blog.none.at/blog/2024/2024-07-02-tls-proxy-tunnel/">&lt;p&gt;Many enterprise networks sit behind a corporate HTTP CONNECT proxy. Applications
that speak TLS natively — think &lt;code&gt;git&lt;&#x2F;code&gt;, &lt;code&gt;curl&lt;&#x2F;code&gt;, SSH-over-HTTPS, or any custom
binary — often have no built-in proxy support. Configuring every single tool is
tedious, fragile, and sometimes impossible when you don’t control the binary.&lt;&#x2F;p&gt;
&lt;p&gt;&lt;code&gt;tls-proxy-tunnel&lt;&#x2F;code&gt; (&lt;code&gt;tpt&lt;&#x2F;code&gt;) solves this at layer 4: it sits between your
application and the outside world, intercepts the TLS connection, extracts the
Server Name Indication (SNI) from the ClientHello, and tunnels the raw bytes
through your corporate HTTP CONNECT proxy — without ever terminating TLS.&lt;&#x2F;p&gt;</description>
      </item>
      <item>
          <title>How does SNI Routing work in HAProxy</title>
          <pubDate>Fri, 17 May 2019 00:00:00 +0000</pubDate>
          <author>aleks</author>
          <link>https://blog.none.at/blog/2019/2019-05-17-haproxy-sni-routing/</link>
          <guid>https://blog.none.at/blog/2019/2019-05-17-haproxy-sni-routing/</guid>
          <description xml:base="https://blog.none.at/blog/2019/2019-05-17-haproxy-sni-routing/">&lt;p&gt;As I travel a lot I faced the problem that in some Wi-Fi networks certain ports are blocked for outgoing communication 😱. The solution is to use software that can handle TCP and HTTP via port &lt;strong&gt;443&lt;&#x2F;strong&gt; so that I can use my Nextcloud and my XMPP client on the same port.&lt;&#x2F;p&gt;</description>
      </item>
    </channel>
</rss>
