We are in the process of getting CFEngine properly configured; for now, 
we are using a manual method.

1.  Login to one machine as root (possible su in a terminal screen).

2.  As root, invoke Firefox (in our case, /usr/lib64/firefox/firefox)

3.  Within Firefox, Help --> About Firefox, and Firefox automatically 
goes to the web to check for updates from an "official" Mozilla site.

4.  If there is an update, let the update complete, and restart Firefox.

5.  Using scp, distribute the /usr/lib64/firefox contents after update 
to all

Note:  if you are having difficulty getting the correct firefox from 
Firefox (the download button), use URL:

http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/21.0/linux-x86_64/en-US/

for the current production Firefox.  As later releases go production, 
replace the 21.0 with the version you want in the event that Firefox 
does not automatically update as in step 3 above.

In principle, from URL:

http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest/linux-x86_64/en-US

one can get the latest stable production release.

Hope this helps.

Yasha Karant

On 06/06/2013 10:19 AM, Ken Teh wrote:
> I'd appreciate some more details on how you implement the Mozilla update
> protocol in an (not quite) enterprise environment.  IOW, not hundreds or
> thousands of machines but enough to make manual updates unfeasable.
>
> Isn't mozilla's update user-based?  When a user launches firefox, the
> browser
> checks for updates, and if there is a newer version, asks the user to
> download
> and install it.  What do you do if the user has no privileges to install
> software?
>
> Thanks!
>
>
> On 06/05/2013 08:40 PM, Yasha Karant wrote:
>> On 06/05/2013 01:57 PM, Ken Teh wrote:
>>> I'd like to hear some pros and cons with using the latest firefox from
>>> mozilla instead of using the ESR version that comes with the stock
>>> distro.  I am deploying a web app that fails to render properly. It is a
>>> bug in firefox which has been fixed since version 18.
>>>
>>> Naturally, the ESR version is 17. Sigh...
>>
>> As we were deploying new Nvidia-equipped stereoscopic 3D scientific
>> visualisation workstations using X86-64 SL6x, we had to make a
>> decision as
>> to whether to use the SL distribution Firefox (ESR) or the latest
>> production
>> release.  After considering the pros and cons (including that the
>> machines
>> are behind a network firewall), we selected the current production
>> version.
>> Thus far, we have had no issues, and have done several updates using the
>> Mozilla Firefox update technique, not the SL6x update, keeping Firefox
>> up to
>> the current production release.  Part of the reason for the decision
>> was the
>> observation you also have made; certain defects that were corrected in
>> the
>> production release did not have the corrections backported to the earlier
>> release ESR SL version.
>>
>> Yasha Karant