<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dig on Aaron&#39;s Worthless Words</title>
    <link>https://a996c8ee.aww-3cz.pages.dev/tags/dig/</link>
    <description>Recent content in Dig on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 16 Oct 2009 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://a996c8ee.aww-3cz.pages.dev/tags/dig/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using SPF Records To Build Objects</title>
      <link>https://a996c8ee.aww-3cz.pages.dev/posts/2009/10/using-spf-records-to-build-objects/</link>
      <pubDate>Fri, 16 Oct 2009 00:00:00 +0000</pubDate>
      <guid>https://a996c8ee.aww-3cz.pages.dev/posts/2009/10/using-spf-records-to-build-objects/</guid>
      <description>&lt;p&gt;My biggest complain about modern firewalls is their lack of the ability to create rules based on URLs or HTTP streams; you have to open access between IP addresses.  Yes, I know there are other means to do that, but I want my ASA/PIX/FWSM to do it without making me do so much work.&lt;/p&gt;&#xA;&lt;p&gt;Anyway, the fact that you have to use IPs brings up some interesting problems.  Let&amp;rsquo;s say you have a server in a DMZ that needs to query Google for some content.  Since you&amp;rsquo;re a hard-ass network guy like I am, you tell the admin that they have provide the data flow they want to use &amp;ndash; source IP, destination IP, protocol, port.  They come back and tell you that they need their server to connect via HTTP to 74.125.45.100.  You put in the rules as given, but the IP has suddenly changed on you.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
