17
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 07 Aug 2023
17 points (81.5% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54443 readers
221 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
@AphoticDev
Unless Google opens it up in revenge, then no, not totally unprotected. But they did set the rooting path to expand the attack surface needlessly.
It's a consequence of locking up your device, so you can't control it to serve as a vehicle for ads, DRM, and data mining.
Security 3rd, otherwise there would be no problems with patching.
F.e. https://www.bleepingcomputer.com/news/security/google-android-patch-gap-makes-n-days-as-dangerous-as-zero-days/
Still one needs to be VERY aware what consequences rooting has.
->
@moosetwin
@AphoticDev
-> (@GrapheneOS offers a good way out of this, but it's only for Google hardware, which is in the race to the bottom with stripping hardware features.)
@moosetwin