<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SRE on Eric X. Liu's Personal Page</title><link>https://ericxliu.me/tags/sre/</link><description>Recent content in SRE on Eric X. Liu's Personal Page</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 12 Sep 2026 21:13:37 -0700</lastBuildDate><atom:link href="https://ericxliu.me/tags/sre/index.xml" rel="self" type="application/rss+xml"/><item><title>A Gitea compromise hidden behind a failed Git sync</title><link>https://ericxliu.me/posts/gitea-compromise-postmortem/</link><pubDate>Sat, 12 Sep 2026 19:31:00 -0700</pubDate><guid>https://ericxliu.me/posts/gitea-compromise-postmortem/</guid><description>&lt;p&gt;A notes repository stopped synchronizing. The cause was a cryptocurrency miner running under Gitea&amp;rsquo;s service account. Killing it didn&amp;rsquo;t help for long: the attacker had changed global Git configuration so that an ordinary fetch could run a script and start it again.&lt;/p&gt;&#10;&lt;p&gt;Gitea and CI went offline for a rebuild. Over September 11-12, recovery restored 301 repositories, object-backed data, SSO, and representative CI workflows. The response also deleted a Coder workspace&amp;rsquo;s home volume. That data was not recovered. Services returned in stages; there isn&amp;rsquo;t a reliable measurement of total downtime.&lt;/p&gt;</description></item></channel></rss>