<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Oom on sgarland.dev</title>
    <link>https://sgarland.dev/tags/oom/</link>
    <description>Recent content in Oom on sgarland.dev</description>
    <generator>Hugo -- 0.147.3</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Dec 2019 03:32:54 +0000</lastBuildDate>
    <atom:link href="https://sgarland.dev/tags/oom/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>XML-RPC, or how to go off on wild goose chases</title>
      <link>https://sgarland.dev/posts/2019-12-04-xml-rpc-or-how/</link>
      <pubDate>Wed, 04 Dec 2019 03:32:54 +0000</pubDate>
      <guid>https://sgarland.dev/posts/2019-12-04-xml-rpc-or-how/</guid>
      <description>&lt;p&gt;XML-RPC, in case you aren&amp;rsquo;t living in the early 2000s, is a remote procedural call (get it?) that encodes its HTTP returns in XML. It has been largely replaced with RESTful APIs, but it still exists. The two places I&amp;rsquo;m personally aware of are rtorrent, and Wordpress. The former I lived with, mainly because nothing was exposed to the internet; the latter I wasn&amp;rsquo;t aware of until today. I thought I had been the victim of a DoS attack using it as a vector but (SPOILER) I don&amp;rsquo;t believe that to be the case.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
