Closed Bug 27012 Opened 23 years ago Closed 22 years ago

Need UI for setting site-specific policies

Categories

(Core :: Security, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED DUPLICATE of bug 38966

People

(Reporter: norrisboyd, Assigned: security-bugs)

References

Details

Currently no way exists to set site-specific policies other than editing a 
preferences file. Need a UI for this.
Guess on target milestone date...
Status: NEW → ASSIGNED
Depends on: 27159
Target Milestone: M16
Bulk moving all Browser Security bugs to new Security: General component.  The 
previous Security component for Browser will be deleted.
Component: Security → Security: General
As a first step, we need a mechanism for maintaining (storing, 
retrieving, testing, removing, adding) site-specific permissions.  The coding in 
nsCookie.cpp which previously handled site-specific cookie policies has now been 
generalized to handle all site-specific permissions.
Steve,
   I'd like to integrate site-specific capabilities storage with the cookie code 
as well, if possible. Some refer to a site (an URL) and some to a 
certificate...will I be able to store per-certificate policies in your cookie 
storage as well?
No, the mechanism as I set it up is for site-specific information only.  But of 
course you could make the certifite look like a pseudo-site and then use the 
mechanism as I implemented it.  Or you could modify the mechanism.
I don't think we'll have time to do this for beta2.
Target Milestone: M16 → M20
Bulk reassigning most of norris's bugs to mstoltz.
Assignee: norris → mstoltz
Status: ASSIGNED → NEW
A nice feature, but it's not going to happen for awhile.
Status: NEW → ASSIGNED
Assigning QA to czhang
QA Contact: junruh → czhang
have you seen bug 38966?


*** This bug has been marked as a duplicate of 27159 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Whoops, wrong duplicate. Sorry for the spam.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---


*** This bug has been marked as a duplicate of 38966 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
Verified dupe.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.