<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Security Round Table &#8211; Episode 3 &#8211; Liability for Vulnerabilities and Responsible Reporting</title>
	<atom:link href="http://www.securityroundtable.com/srt3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.securityroundtable.com/srt3/</link>
	<description>Security Podcasters Discussing Top Issues</description>
	<lastBuildDate>Tue, 25 Sep 2007 16:36:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: gazanga</title>
		<link>http://www.securityroundtable.com/srt3/comment-page-1/#comment-16</link>
		<dc:creator>gazanga</dc:creator>
		<pubDate>Wed, 26 Jul 2006 02:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.securityroundtable.com/?p=12#comment-16</guid>
		<description>I&#039;m not sure if my last post went through.

I enjoyed the podcast but am getting kind of sick of people not being able to lose their objectivity.  They have such a built in hatred for Microsoft that they can&#039;t recognize where they were and where they are.  The old-school, if you don&#039;t wet yourself when you hear *nix, is really short-sighted.  The fact is Microsoft is here to stay.  Their patch schedule is a great idea and is saving enterprises lots of money and allowing them to better calculate risk.  
As Alan said, on a vulnerabilities to user ratio, Microsoft is a better solution for most.  The OS is easier to patch and not that bad.  I will always have an affinity for my *nix flavors, but I know my endusers and CEO will always make me have to support Microsoft.  With that being said, I think that with it being a necessary evil, it&#039;s good to have a reliable patch schedule.

Also as far as the format goes, I really enjoyed a lot of what everyone had to say, with the exception of Martin.  He is a bit long winded and doesn&#039;t really offer anything new or relevant to the conversation.  He&#039;s about 80% B.S. and 20% over his head.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure if my last post went through.</p>
<p>I enjoyed the podcast but am getting kind of sick of people not being able to lose their objectivity.  They have such a built in hatred for Microsoft that they can&#8217;t recognize where they were and where they are.  The old-school, if you don&#8217;t wet yourself when you hear *nix, is really short-sighted.  The fact is Microsoft is here to stay.  Their patch schedule is a great idea and is saving enterprises lots of money and allowing them to better calculate risk.<br />
As Alan said, on a vulnerabilities to user ratio, Microsoft is a better solution for most.  The OS is easier to patch and not that bad.  I will always have an affinity for my *nix flavors, but I know my endusers and CEO will always make me have to support Microsoft.  With that being said, I think that with it being a necessary evil, it&#8217;s good to have a reliable patch schedule.</p>
<p>Also as far as the format goes, I really enjoyed a lot of what everyone had to say, with the exception of Martin.  He is a bit long winded and doesn&#8217;t really offer anything new or relevant to the conversation.  He&#8217;s about 80% B.S. and 20% over his head.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gazanga</title>
		<link>http://www.securityroundtable.com/srt3/comment-page-1/#comment-15</link>
		<dc:creator>gazanga</dc:creator>
		<pubDate>Wed, 26 Jul 2006 02:20:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.securityroundtable.com/?p=12#comment-15</guid>
		<description>I know that roundtables can be difficult but some of the rants were very biased.  It&#039;s the old school, if you defend Microsoft, you&#039;re not a true techy.  You can love *nix and appreciate what Microsoft does.  For example, look at McAfee.  In Feburary, they discovered and patched a vulnerability in EPO.  Last month, a third party finds the hole and announces it.  This requires McAfee to scramble for press releases to get the word out.  A regular update cycle could of helped remedy this.  

Imagine how much better Linux would be if a regular release schedule was available?

Overall you guys are doing well, I just get the idea that Martin is about 80% B.S. and 20% in over his head.  Just my opinion...</description>
		<content:encoded><![CDATA[<p>I know that roundtables can be difficult but some of the rants were very biased.  It&#8217;s the old school, if you defend Microsoft, you&#8217;re not a true techy.  You can love *nix and appreciate what Microsoft does.  For example, look at McAfee.  In Feburary, they discovered and patched a vulnerability in EPO.  Last month, a third party finds the hole and announces it.  This requires McAfee to scramble for press releases to get the word out.  A regular update cycle could of helped remedy this.  </p>
<p>Imagine how much better Linux would be if a regular release schedule was available?</p>
<p>Overall you guys are doing well, I just get the idea that Martin is about 80% B.S. and 20% in over his head.  Just my opinion&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cseifert</title>
		<link>http://www.securityroundtable.com/srt3/comment-page-1/#comment-13</link>
		<dc:creator>cseifert</dc:creator>
		<pubDate>Mon, 24 Jul 2006 12:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.securityroundtable.com/?p=12#comment-13</guid>
		<description>I have enjoyed listening to your discussion on whether and when to disclose vulnerabilities to the public. I recommend the article &quot;Is finding security holes a good idea?&quot; by Eric Rescorla. He is taking an objective take on the issue looking at a cost analysis of the different scenarios.</description>
		<content:encoded><![CDATA[<p>I have enjoyed listening to your discussion on whether and when to disclose vulnerabilities to the public. I recommend the article &#8220;Is finding security holes a good idea?&#8221; by Eric Rescorla. He is taking an objective take on the issue looking at a cost analysis of the different scenarios.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
