Closed Bug 1213921 Opened 5 years ago Closed 5 years ago
Tablet: Secondary user accounts are treated as restricted profile
Reported by "kkus" on IRC. A secondary account created on a tablet is erroneously treated as "restricted profile". Thus all default restrictions are enforced for this user (e.g. No private browsing, no add-ons, ..).
A secondary user has a single active restriction and this breaks our "restricted profile" detection: > no_sms = true
We tweaked this part of the code several times. After further investigation I think the only safe way to detect a restricted profile is to check only the app restriction bundle. This will only contain restrictions if we injected them via the broadcast receiver during profile setup. The user bundle can basically contain whatever and is no clear indicator (On Android M: no_record_audio=false, On a secondary account: no_sms=true).
Tested this on Android M/6.0. As well as on a tablet with normal, secondary and restricted user. This seems to work with all variations now.
Attachment #8673025 - Flags: review?(ally)
Comment on attachment 8673025 [details] [diff] [review] 1213921-restricted-profile.patch Review of attachment 8673025 [details] [diff] [review]: ----------------------------------------------------------------- I would like to hear more about your investigation, but that can wait until we've patched this bug.
Attachment #8673025 - Flags: review?(ally) → review+
Comment on attachment 8673025 [details] [diff] [review] 1213921-restricted-profile.patch Approval Request Comment [Feature/regressing bug #]: Family friendly browsing (Support for "restricted profiles") - Project "KidFox". New feature in Firefox for Android 42. [User impact if declined]: Secondary users on tablets and phone are treated as "restricted profile". Therefore all default restrictions for family friendly browsing will be enforced (No private browsing, No way to clear history, No add-ons, ..) [Describe test coverage new/current, TreeHerder]: Local testing on different devices: Normal profile, Guest profile and Restricted profile. There's no UI test support for restricted profiles yet. [Risks and why]: Low - "Restricted profile" detection has been tested with all known profile types. [String/UUID change made/needed]: -
Comment on attachment 8673025 [details] [diff] [review] 1213921-restricted-profile.patch Sure, taking it. Should be in 42 beta 8.
Verified as fixed on Firefox 42 Beta 8, latest Aurora and Nightly
You need to log in before you can comment on or make changes to this bug.