|
|
| Line 545: |
Line 545: |
|
| |
|
| = design sketch: a 'Corporate Firefox' Toolkit = | | = design sketch: a 'Corporate Firefox' Toolkit = |
|
| |
| == major block: requirement and expectations by it management and support ==
| |
|
| |
| Regardless wether in small nor in medium to largesized corporations:
| |
|
| |
| The requirements, demands, wishes and expectations of it staff and others managing and supporting more than one firefox installations on a network are not considered important by mozilla - neither in the past nor today.
| |
|
| |
| Not even logically following functions are provided, and/or at application level recognized or considered worth action, though they result from the mere facts that:
| |
| - multiple installations on a network require lifecycle management
| |
| - said network is part of an corporate it-infrastructure
| |
| - the existance or demand for network wide policies controlling access to application functions can be expected
| |
| - configuration can be provided in parts or total via network
| |
| -
| |
|
| |
| The following examples outline the impact on real-world scenarios
| |
|
| |
| ===Example: Update sources ===
| |
|
| |
| ==== Problem====
| |
| There is no way to centrally manage the settings for updates sources as well as other installation sites after installation.
| |
|
| |
| ==== Scenario ====
| |
| After the initial deployment, the misspelled servername can only be locally fixed using an 3d- party addon.
| |
|
| |
| There is no way to add a new website to the list of allowed installation sites.
| |
|
| |
|
| |
| ===Example: Firefox and addon lifecycle management ===
| |
|
| |
| ==== Problem ====
| |
| Once distributed, application and addons are essentially 'unmanaged', with installed releases and revisions unknown as well as occured errors during update/upgrades or normal usage.
| |
|
| |
| ==== Usage scenario ====
| |
| The xxy - addon has a severe security problem since update 121, possibly resulting in remote root-access.
| |
|
| |
| Tough luck:
| |
| - One would never know, how many installations have already installed the update and are actually affected.
| |
|
| |
| - Even knowing the affected ones, there`s no roll-back function to move back to the older release.
| |
|
| |
| - The addon can not be globally disabled
| |
|
| |
| - you cannot stop the provision of updates except by redircting dns entries
| |
|
| |
| Boom, showstopper...
| |
|
| |
|
| === design sketch: Toolkit module - Firefox and addon lifecylce management === | | === design sketch: Toolkit module - Firefox and addon lifecylce management === |