Open
Bug 1732143
Opened 4 years ago
Updated 4 years ago
Consider calling SetGroupOwnershipAndPermissions() even if the group owner is not yet admin
Categories
(Toolkit :: Application Update, enhancement, P3)
Tracking
()
NEW
People
(Reporter: bytesized, Unassigned)
References
Details
(Whiteboard: [fidedi-ope])
Currently, we only call SetGroupOwnershipAndPermissions() if we are doing an elevated update or if the group permission is already set to admin.
I think that we should consider calling SetGroupOwnershipAndPermissions() on every update. I don't see any particular reason not to. If we can successfully install an update, we probably also have the privileges necessary to set the permissions this way. And doing this could prevent needing elevation for future updates as other admin users.
| Reporter | ||
Updated•4 years ago
|
Whiteboard: [fidedi-ope]
Updated•4 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•