 




<?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: Javascript Must Die!</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/security-corner/javascript-must-die/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/security-corner/javascript-must-die/</link>
	<description></description>
	<lastBuildDate>Wed, 08 May 2013 20:56:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Ken Harthun</title>
		<link>http://itknowledgeexchange.techtarget.com/security-corner/javascript-must-die/#comment-54</link>
		<dc:creator>Ken Harthun</dc:creator>
		<pubDate>Mon, 09 Nov 2009 23:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/security-corner/javascript-must-die/#comment-54</guid>
		<description><![CDATA[Michael, in my opinion the only other solutions to the problem are to run a browser sandboxed, in a virtual machine, or on a live CD. Our current browser model is so fundamentally broken that it&#039;s almost beyond repair. Your experience mirrors that of many others who have tried NoScript and that just points out how pervasive scripting has become. We are all at risk every time we connect to the Web.]]></description>
		<content:encoded><![CDATA[<p>Michael, in my opinion the only other solutions to the problem are to run a browser sandboxed, in a virtual machine, or on a live CD. Our current browser model is so fundamentally broken that it&#8217;s almost beyond repair. Your experience mirrors that of many others who have tried NoScript and that just points out how pervasive scripting has become. We are all at risk every time we connect to the Web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Morisy</title>
		<link>http://itknowledgeexchange.techtarget.com/security-corner/javascript-must-die/#comment-53</link>
		<dc:creator>Michael Morisy</dc:creator>
		<pubDate>Mon, 09 Nov 2009 16:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/security-corner/javascript-must-die/#comment-53</guid>
		<description><![CDATA[I tried NoScript out again recently when helping a user troubleshoot some issues. The usability problems it presents when browsing a modern web apps just killed it for me: Sure, I&#039;d build a white list up over time, but things would break and, unless I was familiar with the site, I&#039;d never know they were broken.

Are the security threats serious enough that this is necessary? Aren&#039;t there less extreme alternatives out there at this point?]]></description>
		<content:encoded><![CDATA[<p>I tried NoScript out again recently when helping a user troubleshoot some issues. The usability problems it presents when browsing a modern web apps just killed it for me: Sure, I&#8217;d build a white list up over time, but things would break and, unless I was familiar with the site, I&#8217;d never know they were broken.</p>
<p>Are the security threats serious enough that this is necessary? Aren&#8217;t there less extreme alternatives out there at this point?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
