4 ms·
That purpose doesn't really make sense for me. Any IT department that wants to shut down unverified code on their intranet sites will just disable add-ons compl
by detuur 3y ago
That purpose doesn't really make sense for me. Any IT department that wants to shut down unverified code on their intranet sites will just disable add-ons completely. I mean, it's a noble idea, to allow users to install their own preferred add-ons while still blocking them on intranet sites, but for IT it's much easier to just lock it down completely.
I think the feature's simply not finished yet, and that in the future this list is going to come pre-loaded with government and banking domains.
- deleted 3y ago[deleted]
- toyg 3y agoI understand the paranoia but that scenario would make no sense, as long as about:config is accessible - which it will always be, for any FF user except managed-IT ones.
- detuur 3y agoOh, I'm not saying that it's some sort of plot to force us to disable our extensions or anything. I'm saying it's going to be a feature aimed at out-of-the-box security, which advanced users are free to tinker with as they wish. The reality is unfortunately that many less-advanced users are much more likely to install random unvetted add-ons, and sane defaults for that list (pre-loading it with gov and bank domains) will prevent hostile add-ons from doing serious damage.