deploy: teleproxy/teleproxy@f51ea09

Author: rkline0x

changelog/index.html

@@ -1418,6 +1418,17 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#4100" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        4.10.0
+      
+    </span>
+  </a>
+  
 </li>
 
         <li class="md-nav__item">
@@ -1611,6 +1622,17 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#4100" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        4.10.0
+      
+    </span>
+  </a>
+  
 </li>
 
         <li class="md-nav__item">
@@ -1756,13 +1778,15 @@
 
 <h1 id="changelog">Changelog<a class="headerlink" href="#changelog" title="Permanent link">&para;</a></h1>
 <h2 id="unreleased">Unreleased<a class="headerlink" href="#unreleased" title="Permanent link">&para;</a></h2>
-<p>Graceful connection draining on secret removal (<a href="https://github.com/teleproxy/teleproxy/issues/45">#45</a>).</p>
+<h2 id="4100">4.10.0<a class="headerlink" href="#4100" title="Permanent link">&para;</a></h2>
+<p>Graceful connection draining on secret removal (<a href="https://github.com/teleproxy/teleproxy/issues/45">#45</a>) and a brand-new signed RPM repository (<a href="https://github.com/teleproxy/teleproxy/issues/21">#21</a>).</p>
 <ul>
 <li><strong>Zero-downtime secret rotation</strong> — removing a secret from <code>config.toml</code> and sending SIGHUP no longer drops the in-flight connections that were authenticated under it. The slot enters a "draining" state: new connections matching that secret are rejected, but existing ones keep working until they close on their own or <code>drain_timeout_secs</code> (default 300, <code>0</code> = infinite) elapses. Re-adding a draining secret revives the same slot — counters and IP tracking carry over.</li>
 <li>New TOML option <code>drain_timeout_secs</code> (reloadable). Pinned <code>-S</code> CLI secrets are immutable across SIGHUP and never drain.</li>
 <li>New stats: <code>secret_&lt;lbl&gt;_draining</code>, <code>secret_&lt;lbl&gt;_drain_age_seconds</code>, <code>secret_&lt;lbl&gt;_rejected_draining</code>, <code>secret_&lt;lbl&gt;_drain_forced</code>. Same fields exposed in Prometheus as <code>teleproxy_secret_draining</code>, <code>teleproxy_secret_drain_age_seconds</code>, <code>teleproxy_secret_rejected_draining_total</code>, <code>teleproxy_secret_drain_forced_total</code>.</li>
 <li>Slot capacity expanded internally: 16 active secrets at a time as before, plus up to 16 additional draining slots.</li>
 <li>Fixes a latent bug where the per-secret connection counter could go negative if a TLS connection was closed between the TLS handshake and the obfs2 init.</li>
+<li><strong>Signed dnf repository</strong> at <a href="https://teleproxy.github.io/repo/">https://teleproxy.github.io/repo/</a> serving RHEL 9, RHEL 10, AlmaLinux, Rocky Linux, and Fedora 41/42 on x86_64 and aarch64. Install on any of these distros with <code>dnf install https://teleproxy.github.io/repo/teleproxy-release-latest.noarch.rpm &amp;&amp; dnf install teleproxy &amp;&amp; systemctl enable --now teleproxy</code>. Packages are signed with an RSA 4096 / SHA-512 key (RHEL 9 rpm-sequoia compatible). The first install generates a random secret in <code>/etc/teleproxy/config.toml</code>; subsequent <code>dnf upgrade</code> runs swap the binary and never touch user-edited config; <code>dnf remove</code> leaves the config file in place. Built automatically on each tag from the existing static linux binaries via <a href="https://nfpm.goreleaser.com/">nfpm</a>, driven by <code>repository_dispatch</code> from the release workflow into the new <a href="https://github.com/teleproxy/repo">teleproxy/repo</a> repository.</li>
 </ul>
 <h2 id="490">4.9.0<a class="headerlink" href="#490" title="Permanent link">&para;</a></h2>
 <p>PROXY protocol v1/v2 listener support (<a href="https://github.com/teleproxy/teleproxy/issues/50">#50</a>) and per-IP top-N Prometheus metrics (<a href="https://github.com/teleproxy/teleproxy/issues/46">#46</a>).</p>

fa/changelog/index.html

@@ -1418,6 +1418,17 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#4100" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        4.10.0
+      
+    </span>
+  </a>
+  
 </li>
 
         <li class="md-nav__item">
@@ -1611,6 +1622,17 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#4100" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        4.10.0
+      
+    </span>
+  </a>
+  
 </li>
 
         <li class="md-nav__item">
@@ -1756,13 +1778,15 @@
 
 <h1 id="changelog">Changelog<a class="headerlink" href="#changelog" title="Permanent link">&para;</a></h1>
 <h2 id="unreleased">Unreleased<a class="headerlink" href="#unreleased" title="Permanent link">&para;</a></h2>
-<p>Graceful connection draining on secret removal (<a href="https://github.com/teleproxy/teleproxy/issues/45">#45</a>).</p>
+<h2 id="4100">4.10.0<a class="headerlink" href="#4100" title="Permanent link">&para;</a></h2>
+<p>Graceful connection draining on secret removal (<a href="https://github.com/teleproxy/teleproxy/issues/45">#45</a>) and a brand-new signed RPM repository (<a href="https://github.com/teleproxy/teleproxy/issues/21">#21</a>).</p>
 <ul>
 <li><strong>Zero-downtime secret rotation</strong> — removing a secret from <code>config.toml</code> and sending SIGHUP no longer drops the in-flight connections that were authenticated under it. The slot enters a "draining" state: new connections matching that secret are rejected, but existing ones keep working until they close on their own or <code>drain_timeout_secs</code> (default 300, <code>0</code> = infinite) elapses. Re-adding a draining secret revives the same slot — counters and IP tracking carry over.</li>
 <li>New TOML option <code>drain_timeout_secs</code> (reloadable). Pinned <code>-S</code> CLI secrets are immutable across SIGHUP and never drain.</li>
 <li>New stats: <code>secret_&lt;lbl&gt;_draining</code>, <code>secret_&lt;lbl&gt;_drain_age_seconds</code>, <code>secret_&lt;lbl&gt;_rejected_draining</code>, <code>secret_&lt;lbl&gt;_drain_forced</code>. Same fields exposed in Prometheus as <code>teleproxy_secret_draining</code>, <code>teleproxy_secret_drain_age_seconds</code>, <code>teleproxy_secret_rejected_draining_total</code>, <code>teleproxy_secret_drain_forced_total</code>.</li>
 <li>Slot capacity expanded internally: 16 active secrets at a time as before, plus up to 16 additional draining slots.</li>
 <li>Fixes a latent bug where the per-secret connection counter could go negative if a TLS connection was closed between the TLS handshake and the obfs2 init.</li>
+<li><strong>Signed dnf repository</strong> at <a href="https://teleproxy.github.io/repo/">https://teleproxy.github.io/repo/</a> serving RHEL 9, RHEL 10, AlmaLinux, Rocky Linux, and Fedora 41/42 on x86_64 and aarch64. Install on any of these distros with <code>dnf install https://teleproxy.github.io/repo/teleproxy-release-latest.noarch.rpm &amp;&amp; dnf install teleproxy &amp;&amp; systemctl enable --now teleproxy</code>. Packages are signed with an RSA 4096 / SHA-512 key (RHEL 9 rpm-sequoia compatible). The first install generates a random secret in <code>/etc/teleproxy/config.toml</code>; subsequent <code>dnf upgrade</code> runs swap the binary and never touch user-edited config; <code>dnf remove</code> leaves the config file in place. Built automatically on each tag from the existing static linux binaries via <a href="https://nfpm.goreleaser.com/">nfpm</a>, driven by <code>repository_dispatch</code> from the release workflow into the new <a href="https://github.com/teleproxy/repo">teleproxy/repo</a> repository.</li>
 </ul>
 <h2 id="490">4.9.0<a class="headerlink" href="#490" title="Permanent link">&para;</a></h2>
 <p>PROXY protocol v1/v2 listener support (<a href="https://github.com/teleproxy/teleproxy/issues/50">#50</a>) and per-IP top-N Prometheus metrics (<a href="https://github.com/teleproxy/teleproxy/issues/46">#46</a>).</p>

search/search_index.json

@@ -1418,6 +1418,17 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#4100" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        4.10.0
+      
+    </span>
+  </a>
+  
 </li>
 
         <li class="md-nav__item">
@@ -1611,6 +1622,17 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#4100" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        4.10.0
+      
+    </span>
+  </a>
+  
 </li>
 
         <li class="md-nav__item">
@@ -1756,13 +1778,15 @@
 
 <h1 id="changelog">Changelog<a class="headerlink" href="#changelog" title="Permanent link">&para;</a></h1>
 <h2 id="unreleased">Unreleased<a class="headerlink" href="#unreleased" title="Permanent link">&para;</a></h2>
-<p>Graceful connection draining on secret removal (<a href="https://github.com/teleproxy/teleproxy/issues/45">#45</a>).</p>
+<h2 id="4100">4.10.0<a class="headerlink" href="#4100" title="Permanent link">&para;</a></h2>
+<p>Graceful connection draining on secret removal (<a href="https://github.com/teleproxy/teleproxy/issues/45">#45</a>) and a brand-new signed RPM repository (<a href="https://github.com/teleproxy/teleproxy/issues/21">#21</a>).</p>
 <ul>
 <li><strong>Zero-downtime secret rotation</strong> — removing a secret from <code>config.toml</code> and sending SIGHUP no longer drops the in-flight connections that were authenticated under it. The slot enters a "draining" state: new connections matching that secret are rejected, but existing ones keep working until they close on their own or <code>drain_timeout_secs</code> (default 300, <code>0</code> = infinite) elapses. Re-adding a draining secret revives the same slot — counters and IP tracking carry over.</li>
 <li>New TOML option <code>drain_timeout_secs</code> (reloadable). Pinned <code>-S</code> CLI secrets are immutable across SIGHUP and never drain.</li>
 <li>New stats: <code>secret_&lt;lbl&gt;_draining</code>, <code>secret_&lt;lbl&gt;_drain_age_seconds</code>, <code>secret_&lt;lbl&gt;_rejected_draining</code>, <code>secret_&lt;lbl&gt;_drain_forced</code>. Same fields exposed in Prometheus as <code>teleproxy_secret_draining</code>, <code>teleproxy_secret_drain_age_seconds</code>, <code>teleproxy_secret_rejected_draining_total</code>, <code>teleproxy_secret_drain_forced_total</code>.</li>
 <li>Slot capacity expanded internally: 16 active secrets at a time as before, plus up to 16 additional draining slots.</li>
 <li>Fixes a latent bug where the per-secret connection counter could go negative if a TLS connection was closed between the TLS handshake and the obfs2 init.</li>
+<li><strong>Signed dnf repository</strong> at <a href="https://teleproxy.github.io/repo/">https://teleproxy.github.io/repo/</a> serving RHEL 9, RHEL 10, AlmaLinux, Rocky Linux, and Fedora 41/42 on x86_64 and aarch64. Install on any of these distros with <code>dnf install https://teleproxy.github.io/repo/teleproxy-release-latest.noarch.rpm &amp;&amp; dnf install teleproxy &amp;&amp; systemctl enable --now teleproxy</code>. Packages are signed with an RSA 4096 / SHA-512 key (RHEL 9 rpm-sequoia compatible). The first install generates a random secret in <code>/etc/teleproxy/config.toml</code>; subsequent <code>dnf upgrade</code> runs swap the binary and never touch user-edited config; <code>dnf remove</code> leaves the config file in place. Built automatically on each tag from the existing static linux binaries via <a href="https://nfpm.goreleaser.com/">nfpm</a>, driven by <code>repository_dispatch</code> from the release workflow into the new <a href="https://github.com/teleproxy/repo">teleproxy/repo</a> repository.</li>
 </ul>
 <h2 id="490">4.9.0<a class="headerlink" href="#490" title="Permanent link">&para;</a></h2>
 <p>PROXY protocol v1/v2 listener support (<a href="https://github.com/teleproxy/teleproxy/issues/50">#50</a>) and per-IP top-N Prometheus metrics (<a href="https://github.com/teleproxy/teleproxy/issues/46">#46</a>).</p>