| Logger.sys.mjs |
|
578 |
- |
| MessagingSystemAllowlists.sys.mjs |
Remote Settings backed cache that allows for extending the in-tree
messaging-system allowlist off-train. Consumers union their hardcoded
baseline with the getters here, so an empty or unavailable collection means
only items in the baseline list will be allowed.
Records in the `ms-action-allowlists` collection are discriminated by a
`list` field:
{ id, list: "actionOnly", value: "<SpecialMessageAction type>" }
{ id, list: "setPref", value: "<pref name>" }
Three lists decide whether a capability is granted:
1. The in-tree baseline allowlist, hardcoded in the consumer. It always
wins, and adding to it takes a patch and code review. For `actionOnly`
it is ALLOWED_ACTION_MESSAGE_ACTIONS in
_ASRouter._isAllowedActionOnlyMessageAction (ASRouter.sys.mjs); for
`setPref` it is allowedPrefs in SpecialMessageActions.setPref.
2. The in-tree blocklist in MessagingSystemBlocklists.sys.mjs. It discards
matching records from this collection and does nothing else. It cannot
revoke a baseline entry.
3. The records in this collection, which grant whatever survives step 2.
That is: allowed = baseline + (collection records - blocklist). The caches
below hold step 3 only, never the baseline.
|
5621 |
- |
| MessagingSystemBlocklists.sys.mjs |
Denylists for the two messaging-system allowlists that can be extended
off-train through the `ms-action-allowlists` Remote Settings collection (see
MessagingSystemAllowlists.sys.mjs).
Publishing a record to that collection grants a capability to every message
delivered through Nimbus without the code review that gates the in-tree
baseline lists. Entries here can never be granted that way - matching records
are discarded when the collection is read.
This list only ever filters Remote Settings records. Consumers union the
baseline with what survives that filter, so an entry here has no effect if it
is also in the baseline, and it can never revoke a baseline entry. See
MessagingSystemAllowlists.sys.mjs for how the three lists resolve.
To grant something listed here, add it to the baseline allowlist:
ALLOWED_ACTION_MESSAGE_ACTIONS in ASRouter.sys.mjs for actions, allowedPrefs
in SpecialMessageActions.setPref for prefs. Delete its entry here in the same
patch, since the baseline wins and the entry would no longer block anything.
Removing an entry from this file widens what can be granted off-train and
should get security review.
Deliberately absent, and grantable off-train by design: SET_PREF, bounded by
the pref lists below rather than by this one; the set-default actions; and the
pinning actions. These are the capabilities the collection exists to
experiment with.
|
6173 |
- |
| SpecialMessageActions.sys.mjs |
loadAddonIconInURLBar - load addons-notification icon by displaying
box containing addons icon in urlbar. See Bug 1513882
@param {Browser} browser browser element for showing addons icon
|
43879 |
- |
| test |
|
|
- |