Firefox:Extensions:Scratch Pad
Back to Firefox:2.0 PRD
+---------------------------------------------------+ | Extensions | +---------------------------------------------------+ | +-----------------------------------------------+ | | | @@ GMail Notifier 0.3.3 | | | | @@ (^) An update (0.4) is available. | | | | ( Install Now ) ( More Info... ) | | | |-----------------------------------------------| | | | @@ Linky 2.1.0 | | | | @@ Open/download/validate links and pictures | | | |-----------------------------------------------| | | | @@ Magpie 3.1.2 | | | | @@ Media collection tools | | | |-----------------------------------------------| | | | | | | | | | | | | | | | | | | | | | | +-----------------------------------------------+ | | ( * :v) ( Options ) ( Update All ) Get More... /| +-+-----------------------+-------------------------+ | Visit Home Page | | About Linky 2.1.0... | | --------------------- | | Uninstall | | Disable | | Update | | --------------------- | | Move to Top | | Move Up | | Move Down | +-----------------------+
Comments jasonlustig
Will remote blacklisting be done by network administrators, or how? Who exactly is remotely blacklisting extensions? Theoretically if network administrators could blacklist extensions that could be helpful for large deployments because there are certain extensions that they may not want people installing (I'm not sure, maybe games or something in a workplace or school environment).
Comments Silver
I would assume it will be done just like the update configuration, so administrators can set where to get updates and where to get revoke information. I wonder if those should/will be a list of locations, though.
Comments wrprice
An optional pref to the location of a whitelist would be just as useful, if not more so than a blacklist; automatically disallowing the installation of extensions that are not on the approved list of GUIDs. Also, extension/theme signing becomes important so malicious coders don't "steal" another extension's GUID to get around a white/black list.