26 ms·
Although this is an interesting, novel method, there are so many fingerprinting capable APIs in native code that I don't think this matters much. Many apps I u
by jeroenhd 5y ago
Although this is an interesting, novel method, there are so many fingerprinting capable APIs in native code that I don't think this matters much.
Many apps I use daily require internal storage permissions and a bunch of them drop random dotfiles with magical IDs in there. Xiaomi even dumps a world readable unique device ID on the emulated SD card. Not all apps require external storage permissions, but even then there's tons of APIs that can be used to fingerprint the device.
Google is trying their absolute hardest to reduce the fingerprinting surface but as long as system APIs that work with user content like these exist, there will always be something to fingerprint users by. If everything else fails, you could just embed a webview that uses all the javascript stalking we've grown so accustomed to.
It's sad but I don't think you can prevent native code from fingerprinting your device. The sandbox just isn't tight enough and users are too willing to give out permissions.
I can see Google using a predefined set of colours in some update instead of the raw colour values to combat this, but that's only one of many ways apps abuse their users' devices. Unless app stores kick out apps that fingerprint devices, I don't think we'll see any non-fingerprinted devices any time soon.
- gruez 5y ago>Many apps I use daily require internal storage permissions and a bunch of them drop random dotfiles with magical IDs in there. Xiaomi even dumps a world readable unique device ID on the emulated SD card. They're fixing this with soon with scoped storage api.
- a_large_rat01 5y agoA decade later and they're implementing folder permissions...?
- onkoe 5y agoBetter late than never! But.. yikes!
- searchableguy 5y agoAt this point, I am starting to feel permission fatigue.
- SeriousM 5y agoCould fuchsia be the solution to this? It's a fresh start and no company is depending on any of its api. But I guess fuchsia is a flaw for its own because of google...
- bayindirh 5y agoI would assume the opposite. Why a company which makes money from tracking users for many reasons develops an OS which prevents tracking? My guess is that it'd be an OS which would perform tasks Google needs to stay as Google better than Android, and Google may sell these capabilities to devs to further enhance their bottom line.
- nicce 5y agoGoogle cannot change the Linux kernel like they control Chromium or the most of the Android, so with Fuchia (or its kernel) they are more in control once again.
- b112 5y agoGoogle is trying their absolute hardest to reduce the fingerprinting surface Really? If true, it's so they will be the only source of such tracking info. Google is like the one eye, it never stops seeking, looking, tracking you.
- vineyardmike 5y ago> If true, it's so they will be the only source of such tracking info. So... they're reducing their competition? Sounds anti-competitive. They wouldn't know anything about that though.
- amatecha 5y ago"trying their absolute hardest to reduce the fingerprinting surface"... for anyone else :)
- ignoramous 5y agoYes, they indeed are. Though, it could be argued that Google doesn't want anyone else fingerprinting 3B+ Android users other than themselves. Most of their apps ("gapps") are pre-installed with backdoor privileges that can bypass sandbox restrictions in-place for every other (non-OEM) app.
- magicalist 5y ago> Most of their apps ("gapps") are pre-installed with backdoor privileges that can bypass sandbox restrictions in-place for every other (non-OEM) app Hadn't heard about this. Like what?
- ignoramous 5y agoSee: https://grapheneos.org/usage#sandboxed-play-services https://grapheneos.org/usage#sandboxed-play-services
- magicalist 5y agoAh, I see, thanks. I thought you meant like gmail, not play services.
- hansel_der 5y agoi would be kind of surprised if the gmail-app didn't have more access than other email clients
- saurik 5y ago> Unless app stores kick out apps that fingerprint devices, I don't think we'll see any non-fingerprinted devices any time soon. Talk about throwing out the baby with the bath water on making Apple and Google the equivalent of government with the ability to define the rules on all software that anyone can exist without even considering using actual government :(.
- mikeiz404 5y agoNot saying this would be easy but another approach would be to use references to the colors instead of the actual colors. Other color related APIs would have to be updated to accept the references or, if you wanted to add more flexibility, compound color manipulation operations. It would be the responsibility of the renderer, which I am assuming is protected as I am not familiar at all with android, to compute the final color and not reveal it to the app. It wouldn’t be a perfect replacement for actual color values but it would give more flexibility while not revealing the value.
- _jal 5y agoReason #481 virtualization-capable phones would be a huge privacy win.
- bmicraft 5y agoOr just use much lower precision for the color
- ohgodplsno 5y agoAndroid's theming system does not have the ability to dynamically re-set <color> IDs. And, assuming they managed to do so and keep the reference unaccessible to users (because then you could just do context.getColor(android.R.color.material_you_color_primary) to resolve it), you can still access it through reflection.
- jasonjayr 5y agoChasing this dragon is exhausting, and seems to be requiring more user-hostile measures that prevent end users from using their device fully. Can there be a legal frame work where Google and Apple just take your source code and builds it on their farm, and app review is a source-code level review? And Developers that refuse to do these things are just blocked from developing on these platforms?
- mmis1000 5y agoI don't believe there is any company willing to leak their closed source production source code to anyone. And even they do, it is highly likely there are some dependency they use did not come with source at first place. That wouldn't work in any means.
- ohgodplsno 5y agoHanding over your signing keys, your IP, to a company that cannot even be arsed to review apps properly? What could go wrong?
- qwerty456127 5y ago> Many apps I use daily require internal storage permissions and a bunch of them drop random dotfiles with magical IDs in there. Why can't these apps be restricted to certain folders you need them to access? I also feel like apps which abuse file system permissions to modify the user file system (e.g. create files useless to the user), let alone the system file system should be reported and banned. Any app should have full rights to write anything to a special directory dedicated for it however. But you can set up a script to purge it or delete specific files from it on a schedule.
- mPReDiToR 5y agoIsn't this policy how Termux was neutered?
- jeroenhd 5y agoGoogle is working on that with scoped storage, but a lot of old code doesn't work with that yet and dropping the API would break tons of apps. They've been trying to kill general external storage for this reason since Android 4.4, but every time there's huge blowback from users and developers because "they're trying to take our file explorers" or whatever. In KDE Connect you already need to use the modern API to pick a location for file browsing and it works fine. I picked the entire virtual storage area and that's what's available through remote browsing, but I could've picked a single directory. If all apps supported this, we'd be a lot better off. Of course, there's a perverse incentive to put off the transition as long as possible so that stalking libraries can make more money. I think Google is moving very closely to forcing the new API with the release of Android 12, which would mean that most app developers can't really put off updating much longer.
- iggldiggl 5y agoThey could have made the transition much more straightforward by just making the permissions system more granular (i.e. let the user pick a directory instead of simply asking storage access yes/no) and leaving the existing file APIs intact otherwise, just throw a permission error if you're accessing anything outside of the granted scope. Instead they tried to force through a completely new API that isn't compatible with anything that came beforehand, isn't compatible with code that must have a classic file handle and cannot easily be changed (native libraries, parts of the Android API itself), introduces exciting new bugs and has worse performance. Plus at the same time they seem hellbent on hiding the true, original location of files on the file system, so a) if an app needs to ensure continuing access to a file, it needs to copy it to its own storage (Yay, dozens of copies of the same file) b) this breaks any usages and file formats that don't consist of a single, atomic, fully standalone file (HTML files, playlists, subtitles, multi-part archives, ...).