37
What is the scariest permission that an app can have? (iOS and Android)
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Oct 2024
37 points (100.0% liked)
Privacy
31765 readers
363 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
This depends on what you're trying to defend against. In my opinion (on GrapheneOS):
Those are the only permissions that I can think of off the top of my head that could potentially allow an app to phone home. Turning off Wi-Fi for the device does little if the app also has the "Wi-Fi control" permission.
App communication scopes isn't the scary thing, it's the solution. Standard Android sandbox allows apps to communicate if they mutually agree to it. Scopes will allow you to limit that.
I know, but since we're referring to permissions here, I wanted to refer to each of them by the permission names.