-
Notifications
You must be signed in to change notification settings - Fork 527
Default restriction not applied to users not running XPrivacy GUI #1564
Comments
Applications added to a restricted profile get the template applied, I have this seen happen when testing for one of the other issues. Secondary users have their own responsibility to apply restrictions, just like the primary user. If you install XPrivacy for the first time as primary user, there will be no restrictions too. The same is for secondary users. |
We're in a loop, device admin should not give access to XPrivacy GUI to prevent users from changing other users' settings, but we need to give the GUI to have working privacy protection. This is strictly multi-user unfriendly. Please don't forget limited users may have no understanding of what is privacy at all. If we give them limited account it's because they don't have a clue of what they are doing. |
Then you need to setup the restrictions yourself for the secondary user before you hand over your device. |
That would require force deleting other users' password to do so since XPrivacy GUI doesn't allow to manage other users restriction, as stated on #1560 Plus it won't prevent unrestricted rules for apps secondary user may install, resulting in privacy leak. |
A blank profile has no password. |
Of course, but apps installed on a system isn't something fixed that will never change, and once it's given to the end user, there will be a password, because leaving the user account without password is a security issue, that's worse than just a privacy issue. Even without adding new apps, one may get updated and require change in permissions in order to work or protect privacy. |
@Magissia I imagine this must be a lot of work or even impossible to implement via Xprivacy. Have you tried something like AppLock? There are many applications like that, which can lock access to specific applications through a password. You could lock access to the Xprivacy application on your limited user that way. Or does it not block the notification upon a new installation correctly? |
Hello @Cerberus-tm , this is not impossible to implement this via XPrivacy since all users share the same database file, one user could enforce settings to others if the GUI allowed to, i'm sure it's possible to enforce settings manually by editing the database, but it would be long and risky in case of fail as there would be nothing to check if you are doing something wrong. The problem with app lock is the end user may want to use it by itself, forcing me to install a second app lock software just to lock one thing. It also means i will have to force the installation of the app to secondary users (not restricted) witch may have password set, preventing me from configuring the said app locker. Removing other users' password by force is not a solution on a security side, and it is not possible to impressionate other users on Android to configure the app locker. Secondary users could uninstall the applocker themselves, or lead the app locker to crash and still access the XPrivacy GUI. Only app locker that may be fail proof would be one using root or XPosed framework, and there's no plans on giving root to restricted/secondary users, and i didn't seen any app locker using the XPosed framework. |
Have a little patience and I will make global settings per user. You can create an issue for this, so I can provide a test version for it. |
@Magissia This Xposed module seems to be able to lock applications, have you seen it? |
@Cerberus-tm It seemed to be a good idea at first, but multi-user isn't officially available on mobile phone, just on tablet, and tablet doesn't have a dialer. The app itself doesn't seem multi-user friendly at all. But it's a good catch. Edit : The store also says it's not compatible with my devices, even the phones one. @M66B I have patience, but a closed issue is closed. |
Each Android user will get a separate set of settings, so there is no interaction between the users anymore. None of your multi user issues cover this enhancement, so please create a new one. |
Hello, if a new app is given to a user that doesn't have XPrivacy GUI installed and/or enabled, it cause the new app to have absolutely no restriction set.
Something must be found to apply default restrictions even if XPrivacy GUI is not running for the limited/secondary users since disabling XPrivacy GUI is given as solution to #1563 and #1560
Otherwise it may result in privacy leaks.
(Existing rules DO work without the XPrivacy GUI, but XPrivacy GUI is required to apply default model to new apps)
The text was updated successfully, but these errors were encountered: