Closed
Bug 177623
Opened 23 years ago
Closed 4 years ago
Wildcard support for capabilities prefs
Categories
(Core :: Security: CAPS, enhancement)
Core
Security: CAPS
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: hjtoi-bugzilla, Assigned: dveditz)
Details
Instead of doing
pref("capability.policy.mailnews.XMLHttpRequest.channel", "noAccess");
pref("capability.policy.mailnews.XMLHttpRequest.responseXML", "noAccess");
pref("capability.policy.mailnews.XMLHttpRequest.responseText", "noAccess");
pref("capability.policy.mailnews.XMLHttpRequest.status", "noAccess");
...
I want to be able to say
pref("capability.policy.mailnews.XMLHttpRequest.*", "noAccess");
We already seem to have some wildcard support for stuff in the middle of the
capability part, but not at the end.
|
||
Comment 1•22 years ago
|
||
The current wildcard support is kind of a hack. General support would be great
if it could be made efficient. Futuring.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
|
Assignee | |
Updated•19 years ago
|
Assignee: security-bugs → dveditz
Status: ASSIGNED → NEW
QA Contact: bsharma → caps
|
|
Assignee | |
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•