XPrivacy
XPrivacy copied to clipboard
Hundreds of entries in whitelist because entries under "File" cannot be edited
This is my whitelist for Gmail:
The list goes on an on for many pages, I'd estimate I have hundreds of entries like this. And the same issue applies to various other apps I have installed.
Problem:
- I am concerned about performance. The whitelists keeps growing and growing ad infinitum, and Xprivacy needs to go through it every time (presumably).
- Every single time I open a Gmail message that contains an attachment, even if I don't tap on the attachment itself, I have to allow Gmail access to the file individually. This requires several taps every time I open a Gmail message with an attachment, which unnecessarily slows me down and is inconvenient.
- The only 'solution' for me is to give Gmail and other apps access to all my files, which would be rather detrimental to my privacy. The same problem exists for the URL and View whitelists, although the problem is the most serious with File whitelists.
Cause:
The on-demand pop-up offers a few options with wildcards. But the wildcard is always at a fairly low level: I can't simply allow all directories under [email protected]/messages/*
Suggested solution:
Allow expert users to edit the File whitelist. This should let me simply enter [email protected]/messages/*
to solve the problem. The same issue exists for the URL and View whitelists (but it is somewhat less serious there). If there are concerns about breaking things, this could be a feature you have to turn on under expert settings?
Of course I understand if this is somehow not possible. I still like Xprivacy very much!
Question: If it is not possible to change this, what would happen if I exported my Xprivacy settings and edited the file directly, them import it again? Would that work?
And would it also work if I edited the View whitelist in the same way?
Whatever happens, thank you for listening!
Editing the export is currently the only options.
Wow, that is a quick answer! Thanks, I am glad editing the export is possible: I will do that, then, for now.
Do you think editing the whitelist entries directly is possible as a future feature, or is it too complicated / low priority?
+1 For improvements to the white/blacklist functionality.
I think just a couple more default selection would be a huge improvement.
For example, when a URL is requested by an app, allow whitelisting/blacklisting that entire URL on any port. As a specific example, if an app requests foo.facebook.com/bar, allow instantly creating a white/blacklist item to restrict/allow .facebook.com on any port with any protocol.