Talk:Firefox:2.0 Institutional Deployment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ami Ganguli (talk | contribs) (Existing features?) |
||
| Line 8: | Line 8: | ||
I bet some of them want to restrict their users from changing some prefs, too. Startpage may be one, extension server and update URL are sure others. | I bet some of them want to restrict their users from changing some prefs, too. Startpage may be one, extension server and update URL are sure others. | ||
== Existing features? == | |||
Is there a summary of existing lockdown capabilities somewhere? | |||
I think documenting what's available now would a first step, and this by itself is useful itself to enterprise users. Once the existing capabilities (including hidden preferences and tricks) are documented, it should be easier to figure out what's missing. | |||
Revision as of 14:57, 11 March 2005
Comments AxelHecht
Not exactly sure why the scratch pad is on this page, Rafael?
Big corps probably want to host their own update and extension server.
Some institutions (like Banks) may require to lock down extensions completely, or even lock down extensions to their own site.
I bet some of them want to restrict their users from changing some prefs, too. Startpage may be one, extension server and update URL are sure others.
Existing features?
Is there a summary of existing lockdown capabilities somewhere?
I think documenting what's available now would a first step, and this by itself is useful itself to enterprise users. Once the existing capabilities (including hidden preferences and tricks) are documented, it should be easier to figure out what's missing.