<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linux on Rietta Cybersecurity</title>
    <link>https://rietta.com/tags/linux/</link>
    <description>Recent content in Linux on Rietta Cybersecurity</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>1999-2026 Rietta Inc. All Rights Reserved.</copyright>
    <atom:link href="https://rietta.com/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using IPTABLES to Require CloudFlare for All HTTP/HTTPS Traffic</title>
      <link>https://rietta.com/blog/using-iptables-to-require-cloudflare/</link>
      <pubDate>Mon, 10 Sep 2012 00:00:00 +0000</pubDate>
      <guid>https://rietta.com/blog/using-iptables-to-require-cloudflare/</guid>
      <description>For some of our clients, Rietta uses CloudFlare.com for its web application firewall and content distribution network (CDN) services. CloudFlare is installed on a domain by changing the domain&amp;rsquo;s DNS servers to resolve to CloudFlare, which then proceeds to serve as a proxy between the web and the web server running the protected application.&#xA;Once this is setup it is expected that all general web traffic will originate from the CloudFlare network, which is the proxy server.</description>
    </item>
  </channel>
</rss>
