Closed
Bug 777072
Opened 13 years ago
Closed 13 years ago
Update Permission Manager database to handle apps and mozbrowser
Categories
(Core :: General, defect)
Core
General
Tracking
()
People
(Reporter: mounir, Assigned: mounir)
References
Details
(Whiteboard: [qa-])
Attachments
(8 files, 3 obsolete files)
|
9.93 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
|
16.83 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
|
10.24 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
|
7.64 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
|
19.66 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
|
2.57 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
|
5.89 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
|
30.53 KB,
patch
|
justin.lebar+bug
:
review+
|
Details | Diff | Splinter Review |
Permissions should not be given per-origin but per { origin, app, mozbrowser }.
| Assignee | ||
Comment 1•13 years ago
|
||
| Assignee | ||
Comment 2•13 years ago
|
||
Attachment #645496 -
Flags: review?(jonas)
Attachment #645495 -
Flags: review?(jonas) → review+
Comment on attachment 645496 [details] [diff] [review]
Part 2 - AddInternal() and CommonTestPermission() should use nsIPrincipal
Review of attachment 645496 [details] [diff] [review]:
-----------------------------------------------------------------
I'll try to fix this up.
::: extensions/cookie/nsPermissionManager.cpp
@@ +304,5 @@
> const IPC::Permission &perm = perms[i];
> +
> + nsCOMPtr<nsIPrincipal> principal;
> + nsresult rv = GetPrincipalForHost(perm.host, getter_AddRefs(principal));
> + NS_ENSURE_SUCCESS(rv, rv);
This doesn't seem right. We should receive data from the parent process which includes appId+isInBrowserElement
| Assignee | ||
Comment 4•13 years ago
|
||
(In reply to Jonas Sicking (:sicking) from comment #3)
> Comment on attachment 645496 [details] [diff] [review]
> Part 2 - AddInternal() and CommonTestPermission() should use nsIPrincipal
>
> Review of attachment 645496 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> I'll try to fix this up.
>
> ::: extensions/cookie/nsPermissionManager.cpp
> @@ +304,5 @@
> > const IPC::Permission &perm = perms[i];
> > +
> > + nsCOMPtr<nsIPrincipal> principal;
> > + nsresult rv = GetPrincipalForHost(perm.host, getter_AddRefs(principal));
> > + NS_ENSURE_SUCCESS(rv, rv);
>
> This doesn't seem right. We should receive data from the parent process
> which includes appId+isInBrowserElement
The idea was to fix that in another part actually.
Updated•13 years ago
|
blocking-basecamp: ? → +
Updated•13 years ago
|
Blocks: basecamp-permissions
| Assignee | ||
Comment 5•13 years ago
|
||
Attachment #652761 -
Flags: review?(jonas)
| Assignee | ||
Comment 6•13 years ago
|
||
I think next steps are updating nsPermission, IPC::Permission and finally the database.
| Assignee | ||
Comment 7•13 years ago
|
||
I introduced syntax errors with last minute changes.
Attachment #652761 -
Attachment is obsolete: true
Attachment #652761 -
Flags: review?(jonas)
Attachment #652765 -
Flags: review?(jonas)
Comment on attachment 652765 [details] [diff] [review]
Part 3 - Update nsHostTable/nsHostEntry to make them aware of the new security model
Review of attachment 652765 [details] [diff] [review]:
-----------------------------------------------------------------
::: extensions/cookie/nsPermissionManager.h
@@ +53,5 @@
> + /**
> + * PermissionKey is the key used by PermissionHashKey hash table.
> + *
> + * NOTE: It could be implementing nsIHashable but there is no reason to worry
> + * with XPCOM interfaces while we don't need to.
"when we don't need to."
Attachment #652765 -
Flags: review?(jonas) → review+
| Assignee | ||
Comment 9•13 years ago
|
||
With leak/test failures being fixed.
Attachment #652765 -
Attachment is obsolete: true
| Assignee | ||
Comment 10•13 years ago
|
||
Attachment #653811 -
Flags: review?(jonas)
| Assignee | ||
Comment 11•13 years ago
|
||
Attachment #653812 -
Flags: review?(jonas)
Attachment #653811 -
Flags: review?(jonas) → review+
Attachment #653812 -
Flags: review?(jonas) → review+
| Assignee | ||
Comment 12•13 years ago
|
||
Attachment #653870 -
Flags: review?(jonas)
| Assignee | ||
Comment 13•13 years ago
|
||
Now, I have to write tests and fix a leak I haven't been able to reproduce locally yet.
Attachment #645496 -
Flags: review?(jonas) → review+
Attachment #653870 -
Flags: review?(jonas) → review+
| Assignee | ||
Comment 14•13 years ago
|
||
I will merge this with Part 6 before pushing.
Attachment #653942 -
Flags: review?(jonas)
Hmm... do you have code to deal with upgrading existing databases in the user's profile? We don't want to lose any user data when the user installs the next version of firefox.
| Assignee | ||
Comment 16•13 years ago
|
||
(In reply to Jonas Sicking (:sicking) from comment #15)
> Hmm... do you have code to deal with upgrading existing databases in the
> user's profile? We don't want to lose any user data when the user installs
> the next version of firefox.
This is done in "Part 6". You reviewed that patch 2 or 3 hours ago ;)
Attachment #653942 -
Flags: review?(jonas) → review+
| Assignee | ||
Comment 17•13 years ago
|
||
Attachment #654064 -
Flags: review?(jonas)
Attachment #654064 -
Flags: review?(jonas) → review+
| Assignee | ||
Comment 18•13 years ago
|
||
Justin, could you review the tests changes. Everything else has been reviewed by Jonas.
Attachment #653810 -
Attachment is obsolete: true
Attachment #654716 -
Flags: review?(justin.lebar+bug)
Comment 19•13 years ago
|
||
Comment on attachment 654716 [details] [diff] [review]
Part 3 - Update nsHostTable/nsHostEntry to make them aware of the new security model (r=sicking)
Yeesh.
Attachment #654716 -
Flags: review?(justin.lebar+bug) → review+
| Assignee | ||
Comment 20•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/4e0bd449dcb1
https://hg.mozilla.org/mozilla-central/rev/13c586b3c010
https://hg.mozilla.org/mozilla-central/rev/8700d3b9054d
https://hg.mozilla.org/mozilla-central/rev/0e6ed173961e
https://hg.mozilla.org/mozilla-central/rev/a050027d1520
https://hg.mozilla.org/mozilla-central/rev/212b861d4d22
https://hg.mozilla.org/mozilla-central/rev/41f9eeefbee7
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
Backed out, sorry
https://hg.mozilla.org/mozilla-central/rev/eccef9b3f1f1
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 22•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/2b4f2729b401
https://hg.mozilla.org/mozilla-central/rev/0e1c51a8387d
https://hg.mozilla.org/mozilla-central/rev/ef0744b50b61
https://hg.mozilla.org/mozilla-central/rev/789055abc89d
https://hg.mozilla.org/mozilla-central/rev/346a4ed09e06
https://hg.mozilla.org/mozilla-central/rev/961258980236
https://hg.mozilla.org/mozilla-central/rev/5e035bffbad5
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Comment 23•13 years ago
|
||
Can't tell if something is testable from an end-user perspective or not.
Whiteboard: [qa?]
Updated•13 years ago
|
QA Contact: jsmith
| Assignee | ||
Comment 24•13 years ago
|
||
It is testable from an end-user perspective but we have automated tests for that so I think it's not worth doing manual testings.
Comment 25•13 years ago
|
||
(In reply to Mounir Lamouri (:mounir) from comment #24)
> It is testable from an end-user perspective but we have automated tests for
> that so I think it's not worth doing manual testings.
Okay sounds good.
Whiteboard: [qa?] → [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•