<?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"
	>
<channel>
	<title>Comments on: Ask Jesse answer: Mozilla security process</title>
	<atom:link href="http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/</link>
	<description>Jesse Ruderman on Firefox, security, and more</description>
	<pubDate>Thu, 20 Nov 2008 08:27:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Block Sheep</title>
		<link>http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1200</link>
		<dc:creator>Block Sheep</dc:creator>
		<pubDate>Thu, 05 May 2005 04:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1200</guid>
		<description>Re: Getting users to keep Firefox updated

It's get's even more difficult with blunders like this:
* ANOTHER bug in the File Save dialog - MozillaZine Forums - http://forums.mozillazine.org/viewtopic.php?t=228991
* Bugzilla Bug 283730 - https://bugzilla.mozilla.org/show_bug.cgi?id=283730</description>
		<content:encoded><![CDATA[<p>Re: Getting users to keep Firefox updated</p>
<p>It&#8217;s get&#8217;s even more difficult with blunders like this:<br />
* ANOTHER bug in the File Save dialog - MozillaZine Forums - <a href="http://forums.mozillazine.org/viewtopic.php?t=228991" rel="nofollow">http://forums.mozillazine.org/viewtopic.php?t=228991</a><br />
* Bugzilla Bug 283730 - <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=283730" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=283730</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Hecker</title>
		<link>http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1183</link>
		<dc:creator>Frank Hecker</dc:creator>
		<pubDate>Wed, 04 May 2005 17:37:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1183</guid>
		<description>You write "Someone (maybe me) should keep a list of all the security UI in Firefox and ensure the necessary precautions are applied." It would be truly wonderful if you and/or others were to look at the Firefox (and Thunderbird) security UI and figure out how it could be improved, particular for typical users.</description>
		<content:encoded><![CDATA[<p>You write &#8220;Someone (maybe me) should keep a list of all the security UI in Firefox and ensure the necessary precautions are applied.&#8221; It would be truly wonderful if you and/or others were to look at the Firefox (and Thunderbird) security UI and figure out how it could be improved, particular for typical users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nikolas 'Atrus' Coukouma</title>
		<link>http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1180</link>
		<dc:creator>Nikolas 'Atrus' Coukouma</dc:creator>
		<pubDate>Wed, 04 May 2005 13:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1180</guid>
		<description>Re: Getting users to keep Firefox updated
I know a lot of users &lt;i&gt;like&lt;/i&gt; the subtlety of the update notification. In particular, everything on windows pops up with a big bubble demanding attention right now and will continue to harass you every fifteen minutes of your life until you do what it wants.

I definitely think it's good to be noisy and explain it the first time around, but after that it should quiet down. I imagine a dialog with the "don't ask me again" checkbox would make sense. I also think that any noisiness should be confined to critical updates. I really don't need to be pestered to update my extensions.</description>
		<content:encoded><![CDATA[<p>Re: Getting users to keep Firefox updated<br />
I know a lot of users <i>like</i> the subtlety of the update notification. In particular, everything on windows pops up with a big bubble demanding attention right now and will continue to harass you every fifteen minutes of your life until you do what it wants.</p>
<p>I definitely think it&#8217;s good to be noisy and explain it the first time around, but after that it should quiet down. I imagine a dialog with the &#8220;don&#8217;t ask me again&#8221; checkbox would make sense. I also think that any noisiness should be confined to critical updates. I really don&#8217;t need to be pestered to update my extensions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krax [mikx]</title>
		<link>http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1179</link>
		<dc:creator>Michael Krax [mikx]</dc:creator>
		<pubDate>Wed, 04 May 2005 12:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1179</guid>
		<description>Actually i made up my mind on sending advisorys when a patch get's checked in into public CVS. 

I still strongly disagree with this behavior and consider it more or less a full information disclosure, but i dicided to hold my advisorys back in the future until the patch gets released or the bug gets exploited in the wild. Since there is mostly no workaround beside re-compiling on your own or disable javascript (both unlikely actions) triggering an advisory to early doesn't help.

A drasticly too good documented checkin would still make me release an advisory, though. But the Mozilla Security team was doing a good job in doing "obfuscated" checkins lately.</description>
		<content:encoded><![CDATA[<p>Actually i made up my mind on sending advisorys when a patch get&#8217;s checked in into public CVS. </p>
<p>I still strongly disagree with this behavior and consider it more or less a full information disclosure, but i dicided to hold my advisorys back in the future until the patch gets released or the bug gets exploited in the wild. Since there is mostly no workaround beside re-compiling on your own or disable javascript (both unlikely actions) triggering an advisory to early doesn&#8217;t help.</p>
<p>A drasticly too good documented checkin would still make me release an advisory, though. But the Mozilla Security team was doing a good job in doing &#8220;obfuscated&#8221; checkins lately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaell</title>
		<link>http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1177</link>
		<dc:creator>michaell</dc:creator>
		<pubDate>Wed, 04 May 2005 12:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2005/05/04/ask-jesse-answer-mozilla-security-process-internship/#comment-1177</guid>
		<description>Thanks for the comprehensive answer - will be easier to find if I want to point someone to what you've said in the future.

Sounds like (from your internship answer in the next entry) you'll be able to help with some of this stuff when you're there. :)</description>
		<content:encoded><![CDATA[<p>Thanks for the comprehensive answer - will be easier to find if I want to point someone to what you&#8217;ve said in the future.</p>
<p>Sounds like (from your internship answer in the next entry) you&#8217;ll be able to help with some of this stuff when you&#8217;re there. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
