<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://status.sr2.uk/"/>
    <title>Onion Services on SR2® Cloud Status</title>
    <link>https://status.sr2.uk/affected/onion-services/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2026-10-29T14:38:00+00:00</lastBuildDate>
    <updated>2026-10-29T14:38:00+00:00</updated>
    
    
    
      <atom:link href="https://status.sr2.uk/affected/onion-services/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] Hypervisor reboots for Linux kernel vulnerability (postponed)</title>
        <link>https://status.sr2.uk/issues/2026-10-29-hypervisor-reboots-linux-rce/</link>
        <pubDate>Thu, 29 Oct 2026 14:38:00 +0000</pubDate>
        <guid>https://status.sr2.uk/issues/2026-10-29-hypervisor-reboots-linux-rce/</guid>
        <category>2026-10-29 18:00:00</category>
        <description>Update - Having assessed this vulnerability against our infrastructure, we have determined that it is not exploitable. The planned reboots have therefore been postponed. We will post a further update here once we have scheduled the reboots. (08:40 UTC — Oct 30)  A flaw has been disclosed in the Linux kernel&amp;rsquo;s IPv4 TCP implementation (CVE-2026-98432) that could allow a remote attacker to crash an affected system.
To remediate this, we will need to update the kernel and reboot our virtual machine hypervisors.</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Update&lt;/em&gt; - Having assessed this vulnerability against our infrastructure, we have determined that it is not exploitable.
The planned reboots have therefore been postponed. We will post a further update here once we have scheduled the reboots. 
  &lt;span class=&#34;faded&#34;&gt;(08:40 UTC — Oct 30)&lt;/span&gt;

&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;A flaw has been disclosed in the Linux kernel&amp;rsquo;s IPv4 TCP implementation (&lt;a href=&#34;https://access.redhat.com/security/cve/cve-2026-98432&#34;&gt;CVE-2026-98432&lt;/a&gt;) that could allow a remote attacker to crash an affected system.&lt;/p&gt;
&lt;p&gt;To remediate this, we will need to update the kernel and reboot our virtual machine hypervisors. We anticipate that services hosted on each hypervisor may be unavailable for up to 30 minutes while it is rebooted.&lt;/p&gt;
&lt;p&gt;We will update this issue when remediation begins.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Onion Services outage during move to self-signed certificates and software upgrades</title>
        <link>https://status.sr2.uk/issues/2026-10-25-onion-service-certs/</link>
        <pubDate>Sun, 25 Oct 2026 14:00:00 +0000</pubDate>
        <guid>https://status.sr2.uk/issues/2026-10-25-onion-service-certs/</guid>
        <category>2026-10-25T17:20:00&#43;00:00</category>
        <description>Resolved - Onion service hosting has been restored. All onion services are now served with self-signed TLS certificates on the upgraded software stack. (17:20 UTC — Oct 25) Investigating - Onion services are unavailable while we change how TLS certificates are issued for them and upgrade the hosting software. (14:00 UTC — Oct 25) What changed Certificates. Onion services now use self-signed certificates and no longer use certificates from the public WebPKI.</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Onion service hosting has been restored. All onion services are now served with self-signed TLS certificates on the upgraded software stack. 
  &lt;span class=&#34;faded&#34;&gt;(17:20 UTC — Oct 25)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - Onion services are unavailable while we change how TLS certificates are issued for them and upgrade the hosting software. 
  &lt;span class=&#34;faded&#34;&gt;(14:00 UTC — Oct 25)&lt;/span&gt;

&lt;/p&gt;
&lt;h2 id=&#34;what-changed&#34;&gt;What changed&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Certificates.&lt;/strong&gt; Onion services now use self-signed certificates and no longer use certificates from the public WebPKI. Publicly trusted certificate lifetimes keep getting shorter, and we do not have the capacity to keep WebPKI certificates renewed reliably across our onion services. With a self-signed certificate the connection is still encrypted and authenticated end to end by the onion service protocol, because the .onion address is itself derived from the service&amp;rsquo;s key. Browsers that are not Tor Browser may show a certificate warning.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Software.&lt;/strong&gt; We upgraded Onionspray, together with its bundled OpenResty and the C Tor (tor) daemon, to new releases that include recent security fixes.&lt;/p&gt;
&lt;h2 id=&#34;gobalance&#34;&gt;Gobalance&lt;/h2&gt;
&lt;p&gt;We do not use Gobalance in this service, so the recently disclosed Gobalance vulnerability did not affect our services, or pose any risk to the Onion service private keys.&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
