<?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: Big Oops: Mozilla Releases Compromised Vietnamese Language Pack</title>
	<atom:link href="http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/feed/" rel="self" type="application/rss+xml" />
	<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/</link>
	<description>Technology News</description>
	<lastBuildDate>Sun, 22 Nov 2009 18:45:09 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: leland</title>
		<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/comment-page-1/#comment-137924</link>
		<dc:creator>leland</dc:creator>
		<pubDate>Thu, 15 May 2008 03:59:21 +0000</pubDate>
		<guid isPermaLink="false">http://cybernetnews.com/?p=12521#comment-137924</guid>
		<description>That&#039;s what I thought about NoScript as well, but I decided to give it a good try.  What I found was it was so easy to whitelist a site that it really was no harder than normal browsing.  I only whitelist important sites I visit a lot or ones that won&#039;t work otherwise.  Less frequent sites I temporarily whitelist just in case they ever get infected in the future.  One other thing, with NoScript even if you disable the scripting protection you still get the anti-XSS protection.  With the growth of malware delivered through the browser it seems the only safe thing to do unless you want to live in a sandbox like Sandboxie which works quite well for keeping bad stuff out.  Either way just be safe; that&#039;s what is important.</description>
		<content:encoded><![CDATA[<p>That&#8217;s what I thought about NoScript as well, but I decided to give it a good try.  What I found was it was so easy to whitelist a site that it really was no harder than normal browsing.  I only whitelist important sites I visit a lot or ones that won&#8217;t work otherwise.  Less frequent sites I temporarily whitelist just in case they ever get infected in the future.  One other thing, with NoScript even if you disable the scripting protection you still get the anti-XSS protection.  With the growth of malware delivered through the browser it seems the only safe thing to do unless you want to live in a sandbox like Sandboxie which works quite well for keeping bad stuff out.  Either way just be safe; that&#8217;s what is important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/comment-page-1/#comment-137836</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Mon, 12 May 2008 20:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://cybernetnews.com/?p=12521#comment-137836</guid>
		<description>&lt;div class=&quot;commentquote&quot;&gt;&lt;a href=&quot;#comment-137770&quot; rel=&quot;nofollow&quot;&gt;leland wrote:&lt;/a&gt;&lt;blockquote&gt;The only extension I know of that truly increases security in Firefox is NoScript &lt;a href=&quot;http://noscript.net&quot; rel=&quot;nofollow&quot;&gt;http://noscript.net&lt;/a&gt;  It truly does make me feel safer when using Firefox because I decide which sites can run scripts, use plug-ins, and it provides XSS protection.  I love the fact that it puts me in control.  However I definitely tend to stay away from new or unknown extensions unless I am trying it in a Sandbox so I can limit it’s access to the system.&lt;/blockquote&gt;&lt;/div&gt;
I&#039;ve used that NoScript for a little while before, but so many of my favorite sites use JavaScript so it hinders my experience more than anything. What would be cool is if you could automatically have it whitelist a site once you&#039;ve visited it over a dozen times or so. That way the ones you are just skimming through from a Google search and whatnot will have JavaScript disabled.</description>
		<content:encoded><![CDATA[<div class="commentquote"><a href="#comment-137770" rel="nofollow">leland wrote:</a><br />
<blockquote>The only extension I know of that truly increases security in Firefox is NoScript [<a href='http://noscript.net' rel='nofollow'>noscript.net</a>]  It truly does make me feel safer when using Firefox because I decide which sites can run scripts, use plug-ins, and it provides XSS protection.  I love the fact that it puts me in control.  However I definitely tend to stay away from new or unknown extensions unless I am trying it in a Sandbox so I can limit it’s access to the system.</p></blockquote>
</div>
<p>I&#8217;ve used that NoScript for a little while before, but so many of my favorite sites use JavaScript so it hinders my experience more than anything. What would be cool is if you could automatically have it whitelist a site once you&#8217;ve visited it over a dozen times or so. That way the ones you are just skimming through from a Google search and whatnot will have JavaScript disabled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leland</title>
		<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/comment-page-1/#comment-137770</link>
		<dc:creator>leland</dc:creator>
		<pubDate>Sat, 10 May 2008 00:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://cybernetnews.com/?p=12521#comment-137770</guid>
		<description>The only extension I know of that truly increases security in Firefox is NoScript http://noscript.net  It truly does make me feel safer when using Firefox because I decide which sites can run scripts, use plug-ins, and it provides XSS protection.  I love the fact that it puts me in control.  However I definitely tend to stay away from new or unknown extensions unless I am trying it in a Sandbox so I can limit it&#039;s access to the system.</description>
		<content:encoded><![CDATA[<p>The only extension I know of that truly increases security in Firefox is NoScript [<a href='http://noscript.net' rel='nofollow'>noscript.net</a>]  It truly does make me feel safer when using Firefox because I decide which sites can run scripts, use plug-ins, and it provides XSS protection.  I love the fact that it puts me in control.  However I definitely tend to stay away from new or unknown extensions unless I am trying it in a Sandbox so I can limit it&#8217;s access to the system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/comment-page-1/#comment-137763</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Fri, 09 May 2008 20:04:59 +0000</pubDate>
		<guid isPermaLink="false">http://cybernetnews.com/?p=12521#comment-137763</guid>
		<description>&lt;div class=&quot;commentquote&quot;&gt;&lt;a href=&quot;#comment-137717&quot; rel=&quot;nofollow&quot;&gt;Anonymous wrote:&lt;/a&gt;&lt;blockquote&gt;You folks still don’t get it do you?? Mozilla markets Firefox on the fact that it’s suppose too be a more secure browser.  But you can’t go adding a bunch of extensions too something and expect it too remain more secure. Your just adding “possible cracks”, and I’m still “laughing now”. I’m sure Window Snyder is laughing too when she’s not trying too get it patched.  Toldja folks. (Beat up on IE 7 now Firefox faithful)&lt;/blockquote&gt;&lt;/div&gt;
I don&#039;t think anyone would ever deny that using extensions decreases the security of the browser. I know I&#039;ve never said anything along those lines.</description>
		<content:encoded><![CDATA[<div class="commentquote"><a href="#comment-137717" rel="nofollow">Anonymous wrote:</a><br />
<blockquote>You folks still don’t get it do you?? Mozilla markets Firefox on the fact that it’s suppose too be a more secure browser.  But you can’t go adding a bunch of extensions too something and expect it too remain more secure. Your just adding “possible cracks”, and I’m still “laughing now”. I’m sure Window Snyder is laughing too when she’s not trying too get it patched.  Toldja folks. (Beat up on IE 7 now Firefox faithful)</p></blockquote>
</div>
<p>I don&#8217;t think anyone would ever deny that using extensions decreases the security of the browser. I know I&#8217;ve never said anything along those lines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/comment-page-1/#comment-137717</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 08 May 2008 22:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://cybernetnews.com/?p=12521#comment-137717</guid>
		<description>You folks still don&#039;t get it do you?? Mozilla markets Firefox on the fact that it&#039;s suppose too be a more secure browser.  But you can&#039;t go adding a bunch of extensions too something and expect it too remain more secure. Your just adding &quot;possible cracks&quot;, and I&#039;m still &quot;laughing now&quot;. I&#039;m sure Window Snyder is laughing too when she&#039;s not trying too get it patched.  Toldja folks. (Beat up on IE 7 now Firefox faithful)</description>
		<content:encoded><![CDATA[<p>You folks still don&#8217;t get it do you?? Mozilla markets Firefox on the fact that it&#8217;s suppose too be a more secure browser.  But you can&#8217;t go adding a bunch of extensions too something and expect it too remain more secure. Your just adding &#8220;possible cracks&#8221;, and I&#8217;m still &#8220;laughing now&#8221;. I&#8217;m sure Window Snyder is laughing too when she&#8217;s not trying too get it patched.  Toldja folks. (Beat up on IE 7 now Firefox faithful)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/comment-page-1/#comment-137703</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Thu, 08 May 2008 17:52:51 +0000</pubDate>
		<guid isPermaLink="false">http://cybernetnews.com/?p=12521#comment-137703</guid>
		<description>&lt;div class=&quot;commentquote&quot;&gt;&lt;a href=&quot;#comment-137701&quot; rel=&quot;nofollow&quot;&gt;S wrote:&lt;/a&gt;&lt;blockquote&gt;i use the Dr.web  Firefox extension to scan all extension before i install them.
or you can download the extension manually be using save link as on the extension and have your antivirus scan it locally&lt;/blockquote&gt;&lt;/div&gt;
In most cases that will work well, but you still aren&#039;t completely protected. In this situation it took about two months for antivirus apps to pick up on the virus, and so you were left vulnerable for that entire period of time.

&lt;div class=&quot;commentquote&quot;&gt;&lt;a href=&quot;#comment-137702&quot; rel=&quot;nofollow&quot;&gt;Claus Valca wrote:&lt;/a&gt;&lt;blockquote&gt;I am not a programmer, but the Add-on format makes it relatively simple for the average Mozilla user to download, open, and inspect the contents of the Add-on code, prior to installing it.&lt;/blockquote&gt;&lt;/div&gt;
That is one of the beauties with the extensions, but some are so complex that it could take a long time to try and find any insecure parts. Plus, from what I gather with this vulnerability the URL was disguised using HTML encodings. So it&#039;s not like you&#039;re looking for a URL that points to an IP address or something like that.</description>
		<content:encoded><![CDATA[<div class="commentquote"><a href="#comment-137701" rel="nofollow">S wrote:</a><br />
<blockquote>i use the Dr.web  Firefox extension to scan all extension before i install them.<br />
or you can download the extension manually be using save link as on the extension and have your antivirus scan it locally</p></blockquote>
</div>
<p>In most cases that will work well, but you still aren&#8217;t completely protected. In this situation it took about two months for antivirus apps to pick up on the virus, and so you were left vulnerable for that entire period of time.</p>
<div class="commentquote"><a href="#comment-137702" rel="nofollow">Claus Valca wrote:</a><br />
<blockquote>I am not a programmer, but the Add-on format makes it relatively simple for the average Mozilla user to download, open, and inspect the contents of the Add-on code, prior to installing it.</p></blockquote>
</div>
<p>That is one of the beauties with the extensions, but some are so complex that it could take a long time to try and find any insecure parts. Plus, from what I gather with this vulnerability the URL was disguised using HTML encodings. So it&#8217;s not like you&#8217;re looking for a URL that points to an IP address or something like that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claus Valca</title>
		<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/comment-page-1/#comment-137702</link>
		<dc:creator>Claus Valca</dc:creator>
		<pubDate>Thu, 08 May 2008 17:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://cybernetnews.com/?p=12521#comment-137702</guid>
		<description>Yeah,

When I first heard this information on another security site I was initially a bit concerned for two reasons:

1)  Mozilla is often touted (rightly/wrongly) as being a &quot;secure&quot; browser.  I expect to see some finger-wagging and Firefox bashing in the blog-o-sphere out of this.

2) It really is a wake-up call for just downloading and installing Mozilla Add-ons without considering the potential risk...although to my recollection, Mozilla has always been cognizant and public about this risk to its users.

However, I am a bit more relaxed about it for these reasons:

1) Mozilla and the community work hard to ensure these situations don&#039;t happen if the Add-ons are included and downloaded from the approved Add-on site: Mozilla Add-ons - https://addons.mozilla.org/  (Even if in this particular case it actually got in there.)

2) I am not a programmer, but the Add-on format makes it relatively simple for the average Mozilla user to download, open, and inspect the contents of the Add-on code, prior to installing it.

With a good (and free) file compression program (I use 7-Zip) you can unpack the .XPI file Add-ons are bundled up in.

From there you can open almost all of the elements with Notepad or a good freeware alternative (Notepad++) to view the XML/XUL and JavaScript code.

Even if I don&#039;t know all the details of programming, I can probably pick out a suspicious URL and IP calls or other obvious &quot;gothcas&quot; that might warrant a followup email to a Mozilla forum or even the developer to clarify.

Lifehacker has a nice intro: How to build a Firefox extension - http://lifehacker.com/software/programming/how-to-build-a-firefox-extension-264490.php

I guess having a &quot;relatively&quot; secure source for authorized Mozilla Add-ons as well as the format of Add-ons being open for content inspection brings me a bit more comfort.  

But it does certainly brings a bit more pause-before-install to my own Add-on love and usage.</description>
		<content:encoded><![CDATA[<p>Yeah,</p>
<p>When I first heard this information on another security site I was initially a bit concerned for two reasons:</p>
<p>1)  Mozilla is often touted (rightly/wrongly) as being a &#8220;secure&#8221; browser.  I expect to see some finger-wagging and Firefox bashing in the blog-o-sphere out of this.</p>
<p>2) It really is a wake-up call for just downloading and installing Mozilla Add-ons without considering the potential risk&#8230;although to my recollection, Mozilla has always been cognizant and public about this risk to its users.</p>
<p>However, I am a bit more relaxed about it for these reasons:</p>
<p>1) Mozilla and the community work hard to ensure these situations don&#8217;t happen if the Add-ons are included and downloaded from the approved Add-on site: Mozilla Add-ons &#8211; [<a href='https://addons.mozilla.org/' rel='nofollow'>addons.mozilla.org</a>]  (Even if in this particular case it actually got in there.)</p>
<p>2) I am not a programmer, but the Add-on format makes it relatively simple for the average Mozilla user to download, open, and inspect the contents of the Add-on code, prior to installing it.</p>
<p>With a good (and free) file compression program (I use 7-Zip) you can unpack the .XPI file Add-ons are bundled up in.</p>
<p>From there you can open almost all of the elements with Notepad or a good freeware alternative (Notepad++) to view the XML/XUL and JavaScript code.</p>
<p>Even if I don&#8217;t know all the details of programming, I can probably pick out a suspicious URL and IP calls or other obvious &#8220;gothcas&#8221; that might warrant a followup email to a Mozilla forum or even the developer to clarify.</p>
<p>Lifehacker has a nice intro: How to build a Firefox extension &#8211; [<a href='http://lifehacker.com/software/programming/how-to-build-a-firefox-extension-264490.php' rel='nofollow'>lifehacker.com</a>]</p>
<p>I guess having a &#8220;relatively&#8221; secure source for authorized Mozilla Add-ons as well as the format of Add-ons being open for content inspection brings me a bit more comfort.  </p>
<p>But it does certainly brings a bit more pause-before-install to my own Add-on love and usage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S</title>
		<link>http://cybernetnews.com/big-oops-mozilla-releases-compromised-vietnamese-language-pack/comment-page-1/#comment-137701</link>
		<dc:creator>S</dc:creator>
		<pubDate>Thu, 08 May 2008 17:34:28 +0000</pubDate>
		<guid isPermaLink="false">http://cybernetnews.com/?p=12521#comment-137701</guid>
		<description>i use the Dr.web  Firefox extension to scan all extension before i install them.
or you can download the extension manually be using save link as on the extension and have your antivirus scan it locally</description>
		<content:encoded><![CDATA[<p>i use the Dr.web  Firefox extension to scan all extension before i install them.<br />
or you can download the extension manually be using save link as on the extension and have your antivirus scan it locally</p>
]]></content:encoded>
	</item>
</channel>
</rss>
