<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Security flaws in Universal Plug and Play</title>
	<atom:link href="http://blog.pfsense.org/?feed=rss2&#038;p=688" rel="self" type="application/rss+xml" />
	<link>http://blog.pfsense.org/?p=688</link>
	<description>News, reviews and more related to the pfSense firewall project</description>
	<lastBuildDate>Thu, 23 May 2013 04:13:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Anon</title>
		<link>http://blog.pfsense.org/?p=688&#038;cpage=1#comment-21386</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Sat, 18 May 2013 23:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=688#comment-21386</guid>
		<description><![CDATA[mikeisfly: That link gives an error. Seems like the site is a little too paranoid.]]></description>
		<content:encoded><![CDATA[<p>mikeisfly: That link gives an error. Seems like the site is a little too paranoid.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How I Met Your SSH &#124; TechSNAP &#124; Jupiter Broadcasting</title>
		<link>http://blog.pfsense.org/?p=688&#038;cpage=1#comment-20533</link>
		<dc:creator>How I Met Your SSH &#124; TechSNAP &#124; Jupiter Broadcasting</dc:creator>
		<pubDate>Fri, 01 Mar 2013 00:43:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=688#comment-20533</guid>
		<description><![CDATA[[...] week we had a question of uPNP and pfSense &#8211; The pfSense blog has the official answer  &#8211; pfSense uses an updated version of miniupnp, and has always done so, the vulnerable ones [...]]]></description>
		<content:encoded><![CDATA[<p>[...] week we had a question of uPNP and pfSense &#8211; The pfSense blog has the official answer  &#8211; pfSense uses an updated version of miniupnp, and has always done so, the vulnerable ones [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mikeisfly</title>
		<link>http://blog.pfsense.org/?p=688&#038;cpage=1#comment-20203</link>
		<dc:creator>mikeisfly</dc:creator>
		<pubDate>Thu, 07 Feb 2013 00:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=688#comment-20203</guid>
		<description><![CDATA[Steve Gibson of the Spin Rite fame and Shields UP has built a uPNP vulnerability tool at https://www.grc.com/x/ne.dll?rh1dkyd2 . This will check to see if your router is responding to uPNP probe request on your public port. I just checked mine and everything is all good. The first thing I do when setting up residential routers is turn the uPNP setting off. Hope this helps someone.]]></description>
		<content:encoded><![CDATA[<p>Steve Gibson of the Spin Rite fame and Shields UP has built a uPNP vulnerability tool at <a href="https://www.grc.com/x/ne.dll?rh1dkyd2" rel="nofollow">https://www.grc.com/x/ne.dll?rh1dkyd2</a> . This will check to see if your router is responding to uPNP probe request on your public port. I just checked mine and everything is all good. The first thing I do when setting up residential routers is turn the uPNP setting off. Hope this helps someone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Buechler</title>
		<link>http://blog.pfsense.org/?p=688&#038;cpage=1#comment-20014</link>
		<dc:creator>Chris Buechler</dc:creator>
		<pubDate>Sun, 03 Feb 2013 07:32:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=688#comment-20014</guid>
		<description><![CDATA[PV: doesn&#039;t get much easier than our client export with OpenVPN, unless you like the nasty browser-based SSL VPNs which are a real support headache in comparison. Slightly more effort to install up front, but significantly less effort to support on an ongoing basis from what I&#039;ve seen and heard from our commercial support customers.]]></description>
		<content:encoded><![CDATA[<p>PV: doesn&#8217;t get much easier than our client export with OpenVPN, unless you like the nasty browser-based SSL VPNs which are a real support headache in comparison. Slightly more effort to install up front, but significantly less effort to support on an ongoing basis from what I&#8217;ve seen and heard from our commercial support customers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PV</title>
		<link>http://blog.pfsense.org/?p=688&#038;cpage=1#comment-19981</link>
		<dc:creator>PV</dc:creator>
		<pubDate>Sat, 02 Feb 2013 16:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=688#comment-19981</guid>
		<description><![CDATA[Yeah, I&#039;ve always been paranoid about uPnP.  Then again, I&#039;m paranoid about a lot of things dealing with the net.  Mostly of things breaking.  IT is one of those fields where you argue with the directors for the best you can get, and usually have to settle for something far less than what you need.  So far pfsense offers a lot of things that our paid-firewalls just cant match.  Unfortunately our paid firewalls also have some really, really easy to use VPN options for our end users which makes our IT lives much simpler.   If pfsense keeps up the quality I&#039;ve seen and the 2.1 release follows through on that, I&#039;ll be tempted to use it in more than just my home.  IPv6 is something I&#039;m going to need full support for in the next few years.]]></description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;ve always been paranoid about uPnP.  Then again, I&#8217;m paranoid about a lot of things dealing with the net.  Mostly of things breaking.  IT is one of those fields where you argue with the directors for the best you can get, and usually have to settle for something far less than what you need.  So far pfsense offers a lot of things that our paid-firewalls just cant match.  Unfortunately our paid firewalls also have some really, really easy to use VPN options for our end users which makes our IT lives much simpler.   If pfsense keeps up the quality I&#8217;ve seen and the 2.1 release follows through on that, I&#8217;ll be tempted to use it in more than just my home.  IPv6 is something I&#8217;m going to need full support for in the next few years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angus S-F</title>
		<link>http://blog.pfsense.org/?p=688&#038;cpage=1#comment-19949</link>
		<dc:creator>Angus S-F</dc:creator>
		<pubDate>Sat, 02 Feb 2013 01:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=688#comment-19949</guid>
		<description><![CDATA[FWIW the ScanNow tool requires Java.  They have a java-free scanner at this page: &quot;Universal Plug and Play Check by Rapid7&quot; 
http://upnp-check.rapid7.com/]]></description>
		<content:encoded><![CDATA[<p>FWIW the ScanNow tool requires Java.  They have a java-free scanner at this page: &#8220;Universal Plug and Play Check by Rapid7&#8243;<br />
<a href="http://upnp-check.rapid7.com/" rel="nofollow">http://upnp-check.rapid7.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Falha de segurança no UPnP deixa milhões de usuários vulneráveis &#124; pfSense-BR</title>
		<link>http://blog.pfsense.org/?p=688&#038;cpage=1#comment-19932</link>
		<dc:creator>Falha de segurança no UPnP deixa milhões de usuários vulneráveis &#124; pfSense-BR</dc:creator>
		<pubDate>Fri, 01 Feb 2013 14:40:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=688#comment-19932</guid>
		<description><![CDATA[[...] o post do Chris no blog do pfSense sobre a [...]]]></description>
		<content:encoded><![CDATA[<p>[...] o post do Chris no blog do pfSense sobre a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beat</title>
		<link>http://blog.pfsense.org/?p=688&#038;cpage=1#comment-19823</link>
		<dc:creator>Beat</dc:creator>
		<pubDate>Wed, 30 Jan 2013 09:26:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pfsense.org/?p=688#comment-19823</guid>
		<description><![CDATA[Well done guys!

Open source *is* far superior to closed source, and that&#039;s not only just because developers know that others might be looking above their shoulders, and by nature encourages them to follow best practices, but also because of all the open mind that comes with it.

I&#039;m predicting 2013 to be the year where large portions of users start realizing that open source is a better model for everyone.

Keep the great work going! Looking forward to 2.1 with full IPv6 support, as 2013 will also be the year of IPv6 and of a lot of commercial &quot;NAT firewalls&quot; not firewalling anything anymore that is IPv6, as they don&#039;t NAT. ;-)]]></description>
		<content:encoded><![CDATA[<p>Well done guys!</p>
<p>Open source *is* far superior to closed source, and that&#8217;s not only just because developers know that others might be looking above their shoulders, and by nature encourages them to follow best practices, but also because of all the open mind that comes with it.</p>
<p>I&#8217;m predicting 2013 to be the year where large portions of users start realizing that open source is a better model for everyone.</p>
<p>Keep the great work going! Looking forward to 2.1 with full IPv6 support, as 2013 will also be the year of IPv6 and of a lot of commercial &#8220;NAT firewalls&#8221; not firewalling anything anymore that is IPv6, as they don&#8217;t NAT. <img src='http://blog.pfsense.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
