<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BostonGeek &#187; firewall</title>
	<atom:link href="http://www.bostongeek.com/tag/firewall/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bostongeek.com</link>
	<description>We celebrate all facets of geekiness, including Tech Geek, Science Geek and Gaming Geek... coming to you straight from Boston.</description>
	<lastBuildDate>Mon, 23 Feb 2009 14:48:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A sad day for John Hancock employees</title>
		<link>http://www.bostongeek.com/2006/03/24/a-sad-day-for-john-hancock-employees/</link>
		<comments>http://www.bostongeek.com/2006/03/24/a-sad-day-for-john-hancock-employees/#comments</comments>
		<pubDate>Fri, 24 Mar 2006 15:43:30 +0000</pubDate>
		<dc:creator>Colin</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[freedom]]></category>
		<category><![CDATA[john-hancock]]></category>

		<guid isPermaLink="false">http://www.bostongeek.com/2006/03/24/a-sad-day-for-john-hancock-employees/</guid>
		<description><![CDATA[I feel terribly sorry for you, employee of John Hancock.  You aren&#8217;t able to read this fine content any longer.  Why should the employees of John Hancock be denied a little BostonGeek every now and again?  Isn&#8217;t it one of those inalienable rights that our fore-fathers spoke about when drafting the Constitution [...]]]></description>
			<content:encoded><![CDATA[<p><img align="left" title="John Hancock" alt="John Hancock" src="http://static.flickr.com/49/117219279_8346b657f9_o.jpg" />I feel terribly sorry for you, employee of John Hancock.  You aren&#8217;t able to read this fine content any longer.  Why should the employees of John Hancock be denied a little BostonGeek every now and again?  Isn&#8217;t it one of those inalienable rights that our fore-fathers spoke about when drafting the Constitution and signing the Declaration of Independence. Oh yes, the Declaration of Independece which has the signature of, none other than, John Hancock.</p>
<p>Let us think, maybe the company needs to be re-branded.  Maybe the new name could be <em>Pol Pot</em> or <em>Adolf Hitler</em> or <em>George W. Bush</em>.  This might provide a better representation of what the current John Hancock is all about.  A little truth in advertising, if you will.</p>
<p>Of course, I kid.  Honestly, the fact that John Hancock employees cannot reach BostonGeek from work anymore probably has more to do with some crappy content-filtering service in place on a firewall.  And, of course, said content-filtering service has classified BostonGeek as child-porn because the word pedophile was mentioned a thousand times in jest.  Oh well.  Now the employees of John Hancock will have to wait until they are in the privacy of their own home to read BostonGeek.  Surely, this will affect employee morale and John Hancock shall suffer irreparably.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bostongeek.com/2006/03/24/a-sad-day-for-john-hancock-employees/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Barracuda Spam Firewall</title>
		<link>http://www.bostongeek.com/2005/10/13/barracuda-spam-firewall/</link>
		<comments>http://www.bostongeek.com/2005/10/13/barracuda-spam-firewall/#comments</comments>
		<pubDate>Thu, 13 Oct 2005 13:38:09 +0000</pubDate>
		<dc:creator>Carl</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[filter]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://www.bostongeek.com/?p=204</guid>
		<description><![CDATA[I&#8217;m the IT manager at my company.  Woo.  Considering I am a department of exactly one, that means about as much as&#8230; well, as nothing.  It means nothing.  Sorry, I was going somewhere with that simily, but it&#8217;s after ten and I&#8217;m sleepy.
So, to get back to my point, I get [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m the IT manager at my company.  Woo.  Considering I am a department of exactly one, that means about as much as&#8230; well, as nothing.  It means nothing.  Sorry, I was going somewhere with that simily, but it&#8217;s after ten and I&#8217;m sleepy.</p>
<p>So, to get back to my point, I get a lot of cold calls.  For a lot of different products and services.  Some of which make absolutely no sense to me.  Sometimes, though, one actually offers something I just happen to be in the market for.  Enter <a href="http://www.barracudanetworks.com/ns/?L=en">Barracuda Networks</a>, makers of the Barracuda Spam Firewall.<br />
<span id="more-204"></span></p>
<p>I was offered a 30-day trial on this particular piece of hardware, so I took them up on it.  I mean, the buyout price, if it worked, was spectacular, at under $2000 for a 1U rackmount box and about $700 annually for the service subscription.  For an enterprise-level spam filter, that&#8217;s not just a good deal, it&#8217;s a great one.  If it works.  Especially since my company, like all companies, gets inundated with spam.</p>
<p>So I gave them a chance and told them to send one down.  I ordered the <a href="http://www.barracudanetworks.com/ns/products/spam_specs.php">Spam Firewall 300</a>.  A few days later we received the box, opened it, and extracted the thin rackmount appliance with the fish for a logo.  I was surprised at the design.  Didn&#8217;t look like much.  The thought that this machine could cut our spam by 80% or more seemed almost amusingly farfetched.</p>
<p>Set-up was exceedingly simple.  An instruction sheet came with it, indicating how one should use the console to log in and set up things like IP address, passwords, and filtering options.  Walking through those was easy.  We set up our domain names and then physically placed it between our firewall and our email server.  Then we pointed all incoming email to the Barracuda first, so it would then pass on to the Exchange server.  </p>
<p>And that&#8217;s pretty much it.  Basically, the Barracuda is in constant contact with Spamhaus, SpamCop, and Ordb.  Whenever an email comes in from an external email address, the first thing that is checked is the sender domain.  If it is listed at one of those services, it is instantly blocked.  We can also add domains to our own blacklist, though that is rarely necessary.  If a new spam domain gets set up, there is typically a 24-hour lag time before SpamHaus gets it, verifies it, and updates the Spam Firewall.  All automatically.  It has never crashed on me, never hiccupped, and never blocked something it shouldn&#8217;t.</p>
<p>It has, as I mentioned, a blacklist feature.  But it is also highly customizable in other areas.  There is a whitelist (to keep important email addresses and/or domains from getting blocked), filtering of all sorts (so in-depth we rarely actually touch it for anything), and one of my favorite features: logging.</p>
<p>I don&#8217;t mean that the Barracuda just logs incoming and outgoing emails, though it definitely does.  I mean it actually keeps a copy of every email that comes in from an external address or goes out to one, for 30 days.  This is extremely useful when tracking down security breaches, email policy violators, and other ne&#8217;er-do-wells who think that deleting their sent items saves them from being found out.  In my own paradoxical way, I am a Libertarian/Orwellian.  I chafe at the yoke of the system I am a part of, but at the same time&#8230; power is good, when it&#8217;s in my hands.</p>
<p>So here is a box that does it all.  Logs emails, blocks spam, keeps me from having to mess around with ineffective or system-hogging software on the Exchange server.  Needless to say, we bought it.  We&#8217;ve had it for about 6 months now.  And I couldn&#8217;t be happier with it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bostongeek.com/2005/10/13/barracuda-spam-firewall/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
