Closed Bug 1181970 Opened 9 years ago Closed 9 years ago

Restricted Profiles: Do we want to enforce some of the restrictions of Guest profiles?

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Version:
42 Branch
Platform:
All
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox42 affected)

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox42 --- affected

People

(Reporter: sebastian, Unassigned)

References

Details

We already have code to enforce restrictions for guest profiles. Do we want to have some of these restrictions applied to "restricted profiles" e.g. KidFox too? Currently these restrictions are: * DISALLOW_DOWNLOADS * DISALLOW_INSTALL_EXTENSION * DISALLOW_INSTALL_APPS * DISALLOW_BROWSE_FILES * DISALLOW_SHARE * DISALLOW_BOOKMARK * DISALLOW_ADD_CONTACTS * DISALLOW_SET_IMAGE * DISALLOW_MODIFY_ACCOUNTS * DISALLOW_REMOTE_DEBUGGING * DISALLOW_IMPORT_SETTINGS Note that we could always allow the device owner to enable these restrictions (see bug 1180653) but default them to "off" if we think they are not needed by default.
Barbara, Sam: Do you think any of these guest profile restrictions should also be enforced for restricted profiles (by default or optionally)?
Flags: needinfo?(sfang)
Flags: needinfo?(bbermes)
Thanks for checking in, I thought about this again, I feel we should stick to the ones already discussed. It's however good to know that we have options in the future. Thanks for bringing this up.
Flags: needinfo?(bbermes)
No longer blocks: kidfox-v1
Flags: needinfo?(sfang)
Alright. I removed it from kidfox-v1 but left it blocking bug 1125710 so that we can reconsider later.
bbermes: NI-ing you again for FFB phase 2. We are using these restrictions in guest mode. We could easily (famous last words) use them in FFB too. I expect them to be more or less low-hanging fruits. I guess the only ones left exclusively to guest mode are: * DISALLOW_DOWNLOADS * DISALLOW_BROWSE_FILES * DISALLOW_SHARE * DISALLOW_BOOKMARK * DISALLOW_ADD_CONTACTS * DISALLOW_SET_IMAGE If none of these are interesting then let's just close this bug.
Flags: needinfo?(bbermes)
Thanks, I think we should re-consider some of them, I'll add this to the Aha meta feature card, thanks for reminding. Have you already Can you please explain * DISALLOW_SET_IMAGE * DISALLOW_BROWSE_FILES (is this for the restricted profiles files or could this also access the admins files?) I could see this being useful for sure: * DISALLOW_DOWNLOADS * DISALLOW_SHARE I think we don't need or should have the child be able to: * DISALLOW_ADD_CONTACTS * DISALLOW_BOOKMARK
Blocks: family-friendly-browsing-2
Flags: needinfo?(bbermes)
No longer blocks: FFB
(In reply to Barbara Bermes [:barbara] from comment #5) > Can you please explain > * DISALLOW_SET_IMAGE > * DISALLOW_BROWSE_FILES (is this for the restricted profiles files or could > this also access the admins files?) DISALLOW_SET_IMAGE: Setting an image (long-press) as background image (Android launcher). DISALLOW_BROWSE_FILES: Browsing local files (file:///) - only the files of the restricted profile and shared files on the shared external storage.
We decided that we do not need any of these for restricted profiles.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.