<?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: Allow Non-admin Users to Update Firefox</title>
	<atom:link href="http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/feed" rel="self" type="application/rss+xml" />
	<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html</link>
	<description>In with the Out Crowd</description>
	<lastBuildDate>Thu, 02 Sep 2010 04:11:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Remote PC Access Software</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-11565</link>
		<dc:creator>Remote PC Access Software</dc:creator>
		<pubDate>Wed, 02 Jun 2010 22:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-11565</guid>
		<description>Super-Duper web site! I am loving it!! Will arrive back again - taking you feeds also, Thanks.</description>
		<content:encoded><![CDATA[<p>Super-Duper web site! I am loving it!! Will arrive back again &#8211; taking you feeds also, Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-8525</link>
		<dc:creator>Jerry</dc:creator>
		<pubDate>Sun, 15 Nov 2009 12:37:10 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-8525</guid>
		<description>How do you stop the non-administrative accounts on a computer from continuing to try to upgrade, after the upgrade has been performed from the administrative account on that computer?</description>
		<content:encoded><![CDATA[<p>How do you stop the non-administrative accounts on a computer from continuing to try to upgrade, after the upgrade has been performed from the administrative account on that computer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: corey</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-1792</link>
		<dc:creator>corey</dc:creator>
		<pubDate>Thu, 25 Sep 2008 03:25:24 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-1792</guid>
		<description>After trying, this doesn&#039;t work with UAC in Windows Vista</description>
		<content:encoded><![CDATA[<p>After trying, this doesn&#8217;t work with UAC in Windows Vista</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. Abraham</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-1300</link>
		<dc:creator>M. Abraham</dc:creator>
		<pubDate>Thu, 21 Aug 2008 06:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-1300</guid>
		<description>The only solution for this problem is not to use Firefox but IE. Yes, I hate to say that, but if you want the user to work and surf with limited rights (and you really want to do that!) and you also want automatic updates (and you really want that too!) it&#039;s the only way.
If one could integrate third-party-products in this mechanism it would be perfect. (Got to search for that now!)

You could deploy any new versions of Firefox via Active Directory and hope, that the laptops show up within a reasonable time. So the machines don&#039;t need to be online all at the same time but get their software the next time they boot up in you local net.

And no, I don&#039;t know any malware that works like this but to me it&#039;s sounds like a potential way to get passwords easily.</description>
		<content:encoded><![CDATA[<p>The only solution for this problem is not to use Firefox but IE. Yes, I hate to say that, but if you want the user to work and surf with limited rights (and you really want to do that!) and you also want automatic updates (and you really want that too!) it&#8217;s the only way.<br />
If one could integrate third-party-products in this mechanism it would be perfect. (Got to search for that now!)</p>
<p>You could deploy any new versions of Firefox via Active Directory and hope, that the laptops show up within a reasonable time. So the machines don&#8217;t need to be online all at the same time but get their software the next time they boot up in you local net.</p>
<p>And no, I don&#8217;t know any malware that works like this but to me it&#8217;s sounds like a potential way to get passwords easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Woodruff</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-1291</link>
		<dc:creator>Ben Woodruff</dc:creator>
		<pubDate>Wed, 20 Aug 2008 10:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-1291</guid>
		<description>You have a good point about the potential insecurity of doing this, M. Abraham. I&#039;ll do some looking into that when I have a chance. Do you know of any specific malware that would try to take advantage of this?
The problem with using psexec is that we have ~20 workstations about ~5 laptops that are deployed (plus about 3 spares of each). The spares are never turned on and the laptops are rarely on-site. Workstations are only on if the employee who they are assigned to is in the office.
We were able to coordinate having all of those machines on, and on the network, once. We certainly wouldn&#039;t be able to do it every time there was a Firefox update.

I&#039;m not saying that convenience should outweigh security (as that&#039;s completely against my whole philosophy), but in this case it was the only option we could find that was workable.</description>
		<content:encoded><![CDATA[<p>You have a good point about the potential insecurity of doing this, M. Abraham. I&#8217;ll do some looking into that when I have a chance. Do you know of any specific malware that would try to take advantage of this?<br />
The problem with using psexec is that we have ~20 workstations about ~5 laptops that are deployed (plus about 3 spares of each). The spares are never turned on and the laptops are rarely on-site. Workstations are only on if the employee who they are assigned to is in the office.<br />
We were able to coordinate having all of those machines on, and on the network, once. We certainly wouldn&#8217;t be able to do it every time there was a Firefox update.</p>
<p>I&#8217;m not saying that convenience should outweigh security (as that&#8217;s completely against my whole philosophy), but in this case it was the only option we could find that was workable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. Abraham</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-1288</link>
		<dc:creator>M. Abraham</dc:creator>
		<pubDate>Wed, 20 Aug 2008 09:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-1288</guid>
		<description>But if you&#039;re already using psexec you could update all computers by silently installing the new version on all of them:
psexec @active_workstations.txt -u DOMAIN\bwoodruff -c &quot;Firefox Setup .exe -ms&quot;
The -c switch tells psexec to copy the setup-file to the local machine before executing it.
Ok, just one solution that came to my mind while searching. Surely not the perfect one because this need to be done regulary.</description>
		<content:encoded><![CDATA[<p>But if you&#8217;re already using psexec you could update all computers by silently installing the new version on all of them:<br />
psexec @active_workstations.txt -u DOMAIN\bwoodruff -c &#8220;Firefox Setup .exe -ms&#8221;<br />
The -c switch tells psexec to copy the setup-file to the local machine before executing it.<br />
Ok, just one solution that came to my mind while searching. Surely not the perfect one because this need to be done regulary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. Abraham</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-1286</link>
		<dc:creator>M. Abraham</dc:creator>
		<pubDate>Wed, 20 Aug 2008 08:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-1286</guid>
		<description>Giving the user write permission to the Firefox-files is exactly what you don&#039;t want to do. This just undermines the security you gain, when browsing as non-admin. Imagine a virus/trojan-program that the user starts. It might try to replace the Firefox-executable with a modified one that phishes for passwords. It would fail replacing it, if the user has no privileges in this directory.
But don&#039;t ask me for a solution. I came here while searching for one. My idea would have been, to run the Firefox-updater as a service in background. But I don&#039;t know, if this is possible.</description>
		<content:encoded><![CDATA[<p>Giving the user write permission to the Firefox-files is exactly what you don&#8217;t want to do. This just undermines the security you gain, when browsing as non-admin. Imagine a virus/trojan-program that the user starts. It might try to replace the Firefox-executable with a modified one that phishes for passwords. It would fail replacing it, if the user has no privileges in this directory.<br />
But don&#8217;t ask me for a solution. I came here while searching for one. My idea would have been, to run the Firefox-updater as a service in background. But I don&#8217;t know, if this is possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: itismike</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-1175</link>
		<dc:creator>itismike</dc:creator>
		<pubDate>Wed, 06 Aug 2008 19:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-1175</guid>
		<description>If you have rights to modify Group Policy, the permissions can be modified very easily on all PCs, and this method doesn&#039;t rely on every PC being reachable at the time the script is executed:

Computer Configuration&#124;Windows Settings&#124;Security Settings&#124;File System:
%ProgramFiles%\Mozilla Firefox

Configure this file or folder then: Propagate inheritable permissions to all subfolders and files
Permissions
Type Name Permission Apply To:
Allow NT AUTHORITY\Authenticated Users Modify This folder, subfolders and files</description>
		<content:encoded><![CDATA[<p>If you have rights to modify Group Policy, the permissions can be modified very easily on all PCs, and this method doesn&#8217;t rely on every PC being reachable at the time the script is executed:</p>
<p>Computer Configuration|Windows Settings|Security Settings|File System:<br />
%ProgramFiles%\Mozilla Firefox</p>
<p>Configure this file or folder then: Propagate inheritable permissions to all subfolders and files<br />
Permissions<br />
Type Name Permission Apply To:<br />
Allow NT AUTHORITY\Authenticated Users Modify This folder, subfolders and files</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darkdays</title>
		<link>http://ben.woodruff.ws/allow-non-admin-users-to-update-firefox.html/comment-page-1#comment-262</link>
		<dc:creator>Darkdays</dc:creator>
		<pubDate>Fri, 01 Feb 2008 20:08:36 +0000</pubDate>
		<guid isPermaLink="false">http://woodruffrc.com/allow-non-admin-users-to-update-firefox.html#comment-262</guid>
		<description>That &quot;Software Update Failed&quot; message comes up on A LOT of computers at my college.</description>
		<content:encoded><![CDATA[<p>That &#8220;Software Update Failed&#8221; message comes up on A LOT of computers at my college.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
