18 ms·
List of APIs that require declared reasons
- codedokode 3y agoAt the same time popular Linux distributions do almost nothing to prevent fingerprinting.
- fsflover 3y agoYou can use Tor Browser for that.
- codedokode 3y agoI meant fingerprinting by third-party applications like messengers, IDE etc.
- kaba0 3y agoThey have absolutely zero security as well. I love/use them very much, but we really should stop being so naive, it only takes a single bad apple..
- GoofballJones 3y agoGuess the old replies to that of "oh, but it's open source! Anyone can see the code...so there's no need for security because the OS is secure because anyone can see the code! See? Any bugs and they're fixed in like hours. Don't worry!" At least that's what I used to hear all the time. We've now seen that was hogwash.
- vorpalhex 3y agoAppArmor, sandboxing, jails, chroot.. what other feature do you want? Linux will let you have the most locked down box in the world if you want.
- kaba0 3y agoThe only linux distro that has meaningful security is android. Linux sandboxing scene is completely broken for end-user usage, it’s only good for CICD pipelines. If I want to open a file with a program, I don’t want to see an empty drive, neither do I want to kill the program - there should be a proper interaction between the user and the program, like mobile OSs do. Flatpak does have something like that, but only for files and not even that is seamless (plus flatpaks mix packaging with security for no good reason, imo). You literally run basically everything as the same user, every document, family photo is saved, and thus available for r/w by any process, as those share the exact same privilege. This includes that npm install with millions of dependencies as well, that could literally install a screensharing malware with clear access to any internet site and you wouldn’t even notice. The age-old xkcd is still true: the only thing secured is being able to install a video driver.
- vorpalhex 3y agoFlatpak works fine for this. The discord flatpak only has access to my downloads. If I want to tweak that, I run the flatpak customizer UI. It's sort of vaguely annoying to have to restart the app. Or I just run it in docker and only mount what I want. No VM overhead since cgroups are native.
- codedokode 3y agoWhat you are suggesting is basically to write the code yourself. That's equivalent to "Linux distributions do not have proper security out of the box".
- vorpalhex 3y agoNowhere did I suggest anything involving touching code or even raw config file.
- vorpalhex 3y agoThat's blatantly false, you have a variety of tools at hand from VMs to containers to AppArmor policies. Whether those tradeoffs are worth it for you are a decision you can make. "I don't want to make that decision! I want total privacy!" - Great, use Tails which is a distro that goes all in on privacy.
- codedokode 3y agoWhat you suggest is to write a sandbox yourself and solve all the issues (e.g. fix all software to work inside sandbox). For example, software might need an access to a certain DBUS service, but you don't want to grant it an access for all other services. Out of the box DBUS doesn't provide means for that. Out of the box there is no way to prevent an app from getting information about a videocard (e.g. though Vulkan or OpenGL). And so on. Regarding AppArmor, how do you write a policy that would allow a text editor to open only files that user has chosen in Open dialog? In this case we can say that Windows is also absolutely secure - you can just write a kernel driver that would protect sensitive data from applications.
- vorpalhex 3y ago1. Enable AppArmor 2. Done Your distro already has AppArmor files for your distro software. You can also kick it into learning mode if you desire. You could also just stick to flatpaks/snaps - totally sandboxed. You could choose Whonix where every app is an isolated VM. Or choose tails where any egress is locked down and monitored.
- deleted 3y ago[deleted]
- KnobbleMcKnees 3y agoRequiring this for UserDefaults is pretty wild as it will be so far reaching. UserDefaults is also app-scoped so I'm not sure I understand the reason for this as a privacy concern.
- piyuv 3y ago[dead]
- greggsy 3y agoI'm all for transparency - including whether it needs persistent local data
- akmarinov 3y agoThat's not it though - you can still write a file right next to the UserDefaults plist with anything you want without having to declare anything.
- mynameisvlad 3y agoJust because you can still do potentially malicious things through other means does not change the reasoning, intent or need for the UserDefaults change. If you want to write data without providing a reason, then go do that. Until Apple requires reasons for file writes. It’s literally a 2 second process, and it’s meant to provide transparency into what the developer is doing. That seems entirely beneficial to users. Sorry that being honest and taking a few seconds of your time is such a heavy burden.
- lapcat 3y ago> It’s literally a 2 second process, and it’s meant to provide transparency into what the developer is doing. What transparency? Almost every app in the App Store uses UserDefaults, and the only allowed reason to use it is, literally, "CA92.1". How is that transparency? > That seems entirely beneficial to users. How, exactly? > Sorry that being honest and taking a few seconds of your time is such a heavy burden. The dishonest developers will give the exact same "reason" as the honest developers. It's security theater.
- costanzaDynasty 3y agoGreat time to be a dictator. Fingerprints, sexuality, location. "Brilliant people never think of the lives they smash, being brilliant."
- codedokode 3y agoAnd with AI developed by Western engineers it will finally be possible to listen to all phone calls, read all emails and watch video from all cameras. Fully automated people management.
- qwerty456127 3y ago> developers will need to explain why they're using certain APIs. Great! I just hope the same will be introduced on Android. From the very beginning of the smartphones history, I immediately noticed apps put pointless requirements to be given permission for everything and I wanted such a policy to exist. No permission besides those strictly necessary to fulfill the very function of the app should ever be given or even asked for. Nevertheless I'm afraid such clauses increase the power of the vendors like Apple to fight the apps which do whatever they hate even if that is what the user wants.
- the_lego 3y agoDon't hold your breath. XPrivacy software for rooted Android could give fake data to apps 7+ years ago [1], effectively accomplishing what that policy would. But rooting has become more difficult and more undesirable due to SafetyNet, and Google has not implemented such a feature in official Android. They are actively hostile to user control. [1] https://news.ycombinator.com/item?id=36645100 https://news.ycombinator.com/item?id=36645100
- qwerty456127 3y agoYes, I used XPrivacy in the past. But it has became more weird and I don't even understand if it or any successor still is maintained or not.
- folmar 3y agoLuaXPrivacy is not maintained but works and is updated for Android 13.
- realusername 3y agoSlightly unrelated but we really need an equivalent to userscripts on mobile so that users can inject modifications to their apps for adding changes they need. I really liked the xprivacy concept and it should be extended to full scripts.
- 3y ago
- yellow_lead 3y agoApps will find new ways to fingerprint. There's only so much you can prevent on a Turing complete computer.
- user-the-name 3y ago[dead]
- deleted 3y ago[deleted]
- arlcode 3y agoI think, as usual, this will not be solved by a technical cat and mouse game (in which the cat can always decide it likes the advertisement money that comes from tracking after all), but with a piece of paper from the local legislative body appropriate enforcement against app developers. Anything else is bound to not be in the users interest.
- sebzim4500 3y agoIn this case the mouse has superpowers, since it can ban the cat from the app store permanently.
- kaba0 3y agoI don’t think that’s true. It is true for ad blockers-ads, but you can make a completely indifferent execution environment with no access to the outside. Of course you can also just try to learn the movement of cursor/touch screen, but I don’t think that would be accurate enough. People are much more likely to just self-fingerprint themselves.
- labcomputer 3y agoWhile I agree with this, I think the value lies in making the fingerprints less precise. You can think of a fingerprint as akin to a hash of your device's unique ID. If hash collisions are frequent enough, the value of the fingerprint is reduced.
- jadbox 3y agoApple is the bastion of gatekeeping walled gardens. Ofc there is reasons to demand a rationale for certain API feature access, but some of these are pretty common. It seems like they are really demanding more app feature justification in general. It feels that developing apps for Apple is more akin to being an Uber driver where there's very strict guidelines to being an operator. There's zero room to build any platform software [e.g. no side loading, no 3rd party browser engines allowed, no alt payments methods, no emulation, no platform mods, etc].
- tmpX7dMeXU 3y agoI disagree with that analogy. I don’t believe that you’ve raised it in good faith. It just agrees with your view. The situation is the situation, plain and simple. There are too many contextual differences. People have built multi-million and multi-billion-dollar businesses on apps distributed via the App Store. You can’t say the same for Uber drivers. People have built truly differentiated, revolutionary experiences distributed via the App Store. Uber drivers have very little room for differentiation. Be honest.
- aaomidi 3y agoAgreed, the power is no where nearly imbalanced.
- zitterbewegung 3y agoI don’t disagree that they are one of the most restrictive walled gardens but to push the narrative of them valuing security misuse of APIs to fingerprint furthers that. But who are we kidding when this can disrupt current strategies to deliver ads to their users by third parties. Also, if you are pushing some kind of software to a platform you are beholden to the platform. This has been argued to the beginning where software repositories run by corporations can get you kicked off of it. All of what you are saying in the second paragraph have been rules for a long time on the App Store and it is the most lucrative for the App Store to develop for which supports developers . If you want to do what you want using android is an alternative but then you have to remove the shovelware or buy a Pixel. Also the google Play store has less to offer and isn’t well policed since the App Store is more lucrative with more rules.
- anonymouse008 3y agoTIL you can use UserDefaults to access other apps? I knew about AppGroups, but it sounds like they mean brute forcing other applications? By that same token a public CloudKit implementation should need a reason as well? V confused.
- afavour 3y agoAn interesting list: - File timestamp - System boot time - Disk space - Active Keyboard - User Defaults Makes sense but I imagine some of them will also be very annoying, it depends how strict Apple are about giving permission. If you have to maintain a separate record of file change time stamps for example that’s going to get pretty tiring.
- 542458 3y agoI would argue that apps should almost never need access to some of those, like boot time (why?), free space (not meaningful in the era of dynamic offloading to iCloud), and active keyboard (just accept whatever input you’re given). With the benefit of hindsight, User Defaults seems like a bit of a poorly designed API.
- lordgilman 3y agoThey all seem like APIs that could be abused to fingerprint the device, e.g. no two phones are going to have the same free disk space and no two devices behind the same IP address are going to have the same uptime.
- iamcalledrob 3y agoFile timestamp and free space are likely to be used by just about any app that imports a caching library, e.g. for images. I predict a flood of app rejections due to developers unknowingly using these APIs as part of a dependency. Things like stat() are so fundamental that you'll pretty much always find them somewhere in a moderately sized code base.
- 542458 3y agoFile timestamp is a hard one, I’m not really sure what the “correct” way to implement that is while preserving privacy. Maybe hiding timestamps on files not owned by that app? But free space (if being used for caching purposes): Why not just try to save to .cachesDirectory? If there’s no space the file save will fail, which is fine, your app should handle that anyways. If there’s low but sufficient space that fine, the OS will evict the file soon enough.
- nfriedly 3y agoThe list is at https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api https://developer.apple.com/documentation/bundleresources/pr... It includes file time stamps, system boot time, disk space, active keyboard, and user defaults. In each case, it says which specific APIs will be checked and what are allowed and disallowed reasons for apps to use them.
- st3fan 3y agoThe actual list is at https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api https://developer.apple.com/documentation/bundleresources/pr...
- tiim 3y agoLet's hope google starts doing the same soon. But I would be very surprised considering googles business model.
- dangero 3y agoGoogle doing this would just give them a monopoly on fingerprinting Android users
- 58x14 3y agoYears ago I tried to install and sign up for Turo on iOS to rent out a car I owned. It was a luxury car with a rebuilt title. After I put in the VIN of the car, I received an error, and inexplicably I was banned from the app. No notification as to why, no "we don't accept rebuilt title vehicles," nothing. Naturally I scoffed, deleted the app and forgot about it. Last year a friend rented a few cars on Turo for a trip and added me as a driver to one of them. I had switched phone numbers but kept the same phone. I downloaded Turo again and signed up with a new phone number and new email. Before Turo even asked for my driver's license information, I was blocked again. It must be due to fingerprinting, which persisted over years. I'm unsure how much apps can learn about your user profile, other apps you have installed, and other uniquely identifiable data. I've assumed it was limited, but perhaps I've been naive. I guess these new rules are generally good? But I can imagine for every nefarious usage of these APIs, there can be a plausible cover reason...
- loumf 3y agoIt could have been simply some data put in the keychain. That persists through app deletion.
- BillinghamJ 3y agoIt used to. They have largely changed that now - all data is deleted once the last app from a given vendor has been deleted (though it's not instant, and seems to apply weirdly on TestFlight + ad-hoc builds)
- sumuyuda 3y agoI think this behavior hasn’t changed: https://developer.apple.com/forums/thread/36442 https://developer.apple.com/forums/thread/36442
- ec109685 3y agoEverything in this space is so muddled. Deleting the last app from a vendor should erase that data. On the other hand, if you restore your phone from another device, that should never require relogging into anything.
- iamcalledrob 3y agoLaunching a non-trivial app requires so much back-and-forth to get Apple's blessing these days: Special entitlements, business verification, app review, mandatory marketing website etc... It's not a big deal if you're GoogFaceSoft and can throw people at it, but for a solo developer the list of things to deal with is ever increasing. Feels sadly like Apple don't care much about indie developers anymore. The beauty of the web still remains that you can launch something to the world in minutes.
- deleted 3y ago[deleted]
- jeroenhd 3y agoApple, like Google, was naive once, hoping that developers would respect their customers as much as they do (unless you're big enough that kicking you out of the app store would make their products less marketable). They got proven wrong, and had to invent policy after policy to try to fix things. Google has been restricting permissions while Apple has gone even further. Most developers don't need all that much special treatment. Picking between three codes in a few categories isn't really that much work. At least they don't require you to manually email the app reviewers! This stuff only seems to be a major issue for developers trying to use APIs in way Apple does not allow them to be used.
- iamcalledrob 3y ago> Picking between three codes in a few categories isn't really that much work. True, but it's not just that. These changes are just another item to add to the already very long checklist. I'd much rather they add to the App Store ToS "I will not use the following APIs/syscalls for fingerprinting users: [stat, UserDefaults, etc...]" rather than all this busywork. Since these restrictions are enforced by the review team (vs. the OS), the end result is the same.
- sebzim4500 3y agoI would imagine that a description of what the api is being used for makes life way easier for the review team to check whether you are telling the truth.
- nerdjon 3y agoI am curious if they will go back and look at apps that are accessing these API's or will only look at them when there is an update? I am wondering if we will be seeing another situation where certain apps delay updates like with the previous app tracking permissions. Also curious if they would ever go so far as to add a notice of something like "this app could possibly be fingerprinting you" in the App Store or if they are confident enough in asking about these permissions that they will feel they won't need to alert users.
- reaperducer 3y agoI am curious if they will go back and look at apps that are accessing these API's or will only look at them when there is an update? With the earlier privacy crackdown that upset Facebook and Google so much, it only applied to new and updated apps. According to people on HN, that's why it took Google months and months to issue an update to its apps, and during that time it continued Hoovering up people's information. There are lots of apps on the app store that haven't been updated since the last round of privacy rules came out, which tells you a lot about those developers.
- asow92 3y agoAs an app developer, I have to say that Apple has made it increasing more difficult to provide a seamless user experience to our users over time. Yes, there are plenty of bad actors out there, and they ruin it for the rest of us who collect data only for the purpose of driving the experience forward. The biggest recent pain point that comes to mind is cracking down on accessing the pasteboard without prompting the user for access first. The pasteboard was an essential piece for enabling seamless universal links in many apps. Universal links allow us to give our users the best possible first impression and make things easy for them. Mind you, most users _need_ to be guided along most experiences, don't read things, and blame you for when they can't read. At some point the value prop of apps is going to be completely negated by how difficult they are to use.
- eropple 3y agoIt's been a while, so correct me if I'm wrong, but a "Share -> Copy" action doesn't require permissions, does it? That's the conventional way to do this in Apple's own apps and a user should be able to be expected to follow that if they want to copy a link. (Doing otherwise would be nonstandard and surprising to me, regardless.) Otherwise, accessing UIPasteboard should require permissions. Sorry for Your Flow, but like--the app needs to be transparent about what it's doing, and dirtbags exist, so.
- asow92 3y agoWhile that works, it's not very user friendly, and that means friction, and friction means churn, and churn means a sad boss. It makes obvious sense to us, but gramma or your luddite uncle have a hard time with that. They need to be redirected (handheld) to where they're going.
- eropple 3y agoIt absolutely does, and I'm sure your boss doesn't like to hear it, but falling out of your flow is a pretty small price to pay for somebody else not being able to scrape Grandma's credit card off the pasteboard. I want my tech-averse relatives to bail out of an app when they see that unless they're hand-held through it and the reasoning is made sufficiently apparent that they can parse it. If they can't, it's not clear enough, and they (and the OS) should default to no.
- remote_phone 3y agoBasically, decompile the Facebook and Instagram apps, and any tricks they are using to circumvent privacy should be squashed.
- sdflhasjd 3y agoAt some point, I've just come to hate app development. Everything's been ruined by the collateral damage from unscrupulous developers and the war the app stores wage on them, the rent-seeking the platforms engage in, the bullshit rules and shitty review process. The general rot and entropy of it all. UserDefaults... really? Let's give Google more control over the web so they can finally the destroy it in the same way and there can no longer be anything for me to care about.
- seanalltogether 3y agoHold on, Apple is restricting access to UserDefaults? Is there an app out there that DOESN'T use UserDefaults to save various app settings? Data saved there is already scoped to the app itself, not to other apps or system information
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- pininja 3y agoCan this scope be shared in some way if you’re the owner of multiple apps? I thought it was strange seeing Threads listed as a 12+ year old app when I know it’s brand new… it gave me the feeling someone could just fudge numbers and more if they’re clever.
- mosen 3y agoI think that’s the age rating for the app.
- pininja 3y agoOh wow, I’ve misread that for as long as it’s been there. It doesn’t look like a button, but tapping it scrolls the page down to age rating.
- tailspin2019 3y agoGlad I’m not the only one. Even after I eventually realised it’s the age rating and not the age of the app itself, I still find myself constantly forgetting this because it’s so unintuitive. There is something about the way it’s presented (or maybe a bug in my brain) that keeps reading it as the age of the app. (And IMHO that would be a lot more useful thing to show in that prominent position too)
- 3y ago
- amiga386 3y agoAre you kidding me? stat() ? Of course, the make command must be spying on you. rsync. cp. tar. find. "I need to see if this inode has S_ISDIR set, so I can walk the directory tree." "How dare you invade the user's PRIVACY!" I can't see why anyone would willingly choose an "app" when they can still run normal software on macos.
- mynameisvlad 3y agoYou know that you could just… provide that reason and get approved, right? Apple isn’t banning the use of these APIs. It just requires you as a developer to actually be transparent and honest about the things that could potentially fingerprint a user. To make that sound like a bad thing because you’re lightly inconvenienced is an interesting take.
- amiga386 3y agoMaybe this is just a clash of cultures, but I expect to type "gcc myprog.c" on one computer, give the resulting executable to someone running the same hardware+OS, and have it just work. I don't want to be forced to enter into a contract with Apple and pay them fees to be permitted to produce software that can run on my friends' computers. I don't want them to be able, with the snap of their fingers, to remotely disable all software I've ever made, for whatever reason they deem just, like if I besmirched the good name of their leader on Twitter. I think Apple's an awful company slowly enclosing the commons that is general purpose computing, so that it make phat bank by forcing itself as a middleman between anyone who uses their hardware and anyone who writes software for those people. I don't encourage anyone to use Apple products so I write software that can be used on almost any platform, but can also be used on Apple if you compile it correctly. Hence why stat() piques my interest, and some obj-c/swift nonsense does not. I resent any further restrictions on distribution or usage. I should not have to justify myself or my code to Apple. I should have to justify myself to the users that be run it, and the user should have all the tools necessary to see what I'm doing in my code (e.g. wouldn't it be nice if macos hadn't crippled dtruss by default) I don't think it's a light inconveniencing. I think it's further encroachment on the freedom to run any software on your computer for any purpose, being done to privately enrich Apple, under the marketing guise of benefit to their users.
- frameset 3y agoPlease bring on the app sideloading EU. I am tired of this app store bullshit.
- GoofballJones 3y agoMaybe use Android. You can sideload to that. Why even use an iPhone at all if all you want to do is bypass the appstore and sideload apps anyway? Get a great Android flagship phone with all it's bells and whistles on it and sideload away to your heart's content. I don't know, Apple is trying to stop bad actors from fingerprinting users and violating privacy etc. Or maybe you're into that?
- frameset 3y agoI have android phone. I develop a cross platform application (FOSS). Every time I push an update to the app store version it's easily 4x the work of the play store equivalent. I also have to pay apple £80 for the privilege of having my app available for free on their platform. I would just like to be able to provide users a file and say "here you go, install this" so I don't have to pay apple to bless my software.
- drexlspivey 3y agoOh no you have to pay £80 to gain access to a few billion users, and automatically push updates to them. Maybe don’t pay the fee if you think it’s not worth it.
- halleys_comet69 3y agoThe issue is not that you have to pay to put your software on the App Store, it’s that the only way to run your software on the hardware you and your users own is to put it in the App Store.
- GoofballJones 3y agoYes, sideloading is the key. Meanwhile, from just today: https://arstechnica.com/security/2023/07/android-malware-uses-ocr-to-capture-credentials-displayed-on-phone-screens/ https://arstechnica.com/security/2023/07/android-malware-use...
- dmix 3y agoI've long wondered whether clicking "Ask not to track" when opening a new app for the first time actually does what it says.
- SoftTalker 3y agoApple: We ask for your actual fingerprint and other biometrics, but it's fine when we do it. Nobody else can though. Trust us.
- scarface_74 3y agoWell, you can always not enroll in FaceID and TouchID and use a passcode.
- GoofballJones 3y agoI take it you don't use Apple products, because there are a bunch of 3rd-party apps out there that use the Face-ID or Touch-ID all the time. For instance the password manager 1Password uses biometrics to get into the app, if you choose.
- SoftTalker 3y agoI use an iPhone but I don't have FaceID or TouchID set up.
- GoofballJones 3y ago"That's all going to the government! I ain't gonna use that!" ok...
- flutas 3y agoMan, I'm seeing such disingenuous takes from you all over this thread. From "just get an android" in response to someone complaining about having to pay $100/yr to publish a FOSS app on the App Store to "I take it you don't use apple products" or "That's all going to the government! I ain't gonna use that!" when someone only mentioned not setting up Touch ID or Face ID. Maybe read, think, and then don't reply with snark. While I do agree with this change, this restriction also clearly serves to further entrench Apple to be the gatekeeper over users. They can fingerprint you, they can serve ads to you, but oh anyone else no no no, that's evil and against your privacy™
- RcouF1uZ4gsC 3y agoI wonder if we will see more privacy focused action by Apple on its App Store in the near future. With them being forced to allow for 3rd party app stores, they will go all in on trying to convince people that their App Store is the one for privacy and safety and that people are risking their privacy and safety by installing another App Store. By having to compete against other potential app stores, they are incentivized to lean in further into privacy to set themselves apart.
- dang 3y agoSome background here: App Store to require developers to describe why their apps use certain APIs - https://9to5mac.com/2023/07/27/app-store-describe-app-api/ https://9to5mac.com/2023/07/27/app-store-describe-app-api/ Apple cracking down on 'fingerprinting' with new App Store API rules - https://www.engadget.com/apple-cracking-down-on-fingerprinting-with-new-app-store-api-rules-080007498.html https://www.engadget.com/apple-cracking-down-on-fingerprinti... (via https://news.ycombinator.com/item?id=36905295 https://news.ycombinator.com/item?id=36905295, but we merged that thread hither)
- jononomo 3y agoI was installing the Discord desktop app on an old MacBook earlier today and I got a prompt along the lines of "Discord would like to monitor every keystroke you enter in every application on this computer -- hit OK to continue." I very carefully selected "Hell no" and I honestly felt offended even to have been asked that question. It would be like some random person on the subway just asking if they could have all the money in my wallet. I felt like I was being pranked. If you're going to be that audacious, at least give me the respect of explaining why. Just asking me that with "ok" or "no" as my only options to proceed is ridiculous.
- sophiebits 3y agoIf I’m not mistaken, this is for a global push-to-talk shortcut that works even when Discord is not focused. Not sure if Apple provides an opportunity for apps to show a reason in the prompt.
- PsychoOil 3y ago[dead]