Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

Do not restrict the pro enabler on new install #812

Closed
M66B opened this issue Nov 22, 2013 · 5 comments
Closed

Do not restrict the pro enabler on new install #812

M66B opened this issue Nov 22, 2013 · 5 comments

Comments

@M66B
Copy link
Owner

M66B commented Nov 22, 2013

The allow restricting the pro enabler later.

@M66B M66B closed this as completed in 97d51c4 Nov 23, 2013
@Cerberus-tm
Copy link

Do you mean on a new install of Xprivacy itself (not the enabler), as opposed to an update?

And do you mean, do not restrict any permission for the enabler? Or not the relevant ones?

@M66B
Copy link
Owner Author

M66B commented Nov 23, 2013

No restrictions (all) will be applied when installing the pro enabler.
This is to allow manual restriction of the pro enabler.

@Cerberus-tm
Copy link

I'm afraid I don't understand...but I'm sure things will be all right if I just go about using Xprivacy as I'm used to? No restrictions will be applied by what/whom, what does that mean? Do I need to do something special, or not?

@M66B
Copy link
Owner Author

M66B commented Nov 24, 2013

You don't have to do anything, just enjoy using XPrivacy ;-)

@Cerberus-tm
Copy link

Yay! That happens to be exactly what I'm doing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants