8 ms·
Android 13’s new sideloading restriction of Accessibility APIs
- rektide 5y agoAbsolutely capital dogshit move, a direct slice at the jugular for user freedoms, for letting people do computing in their terms. The presence of bad actors keeps being used as ammunition to destory possibility, to end softness, to make computing hard & inflexible, and it's the same genetic makeup as the constant cowtowing to fear that let's 'think of the children' be the deciding & only opinion policy gets passed with. Loathsome detestable & massive setback, colossal unwinding of Android's spiritual advantage versus The Loyal Opposition Apple. If both platforms collapse into anti-choice, what happens to Apple's defense that it's users can go elsewhere? These shackles we permit to be set upon us, this prohibition of sideloading, the anti-generalization of computing can only be defended against by principled stances. For eroding possibility is forever to the megacorporate bottom line's profit. What a degrading trashfire move, Google, responding to the bad at such vast setback & penalty for the very very very good. Unlocking & exposing applications in new & amazing fashions is one of the highest & most virtuous goods, one of the best things we can do- reenable some unknown, go further- and this move speaks of a desire to embrace old stasist ossifying & cold death, to make us all rot forever with whatver is or was.
- ars 5y agoNice rant. But the headline leaves out a lot of detail that is in the article, which negates your rant.
- wtallis 5y ago"The feature still exists, behind a dark pattern of undiscoverability" really isn't as good of an excuse as you seem to think it is.
- selfhoster11 5y agoThey didn't remove the feature. It's simply been moved to the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of the Leopard".
- deleted 5y ago[deleted]
- selfhoster11 5y agoI disagree. The very presence of these headlines indicates exactly what both the parent and myself are afraid of: that Android is losing uselessness for power users. The rant is far from being untrue.
- selfhoster11 5y agoThat comment was one rollercoaster of a ride. Very poetic, in a good way. Android was my favourite smartphone OS since it championed user freedom. Now that this freedom is reduced, there isn't much holding me there vs, for example, iOS.
- josephcsible 5y agoAs bad as moves like this are for freedom, even if Google did 20 more like it, Android would still be much freer than iOS.
- selfhoster11 5y agoI'm not so sure. Rooting a phone or flashing a custom firmware breaks Safety net, which means a good portion of apps that I find important will not run on my phone. An unrooted/unmodded device can be really annoying to use depending on what the manufacturer put in the ROM. I can't really think of a single thing beyond "sideloading" (what a repulsive word) apps and maybe filesystem/SD card access that Android has as an advantage over iOS, while the list of disadvantages keeps getting longer.
- josephcsible 5y agoI agree that's a big problem, but it's still less bad than iOS where you just can't flash a custom firmware. And sideloading is a really, really big thing.
- selfhoster11 5y agoWhile I can flash it, it's very unlikely that I actually will due to the invalidation of the SafetyNet status that I mentioned. If I can't make use of this feature without losing apps I care about, then I might as well treat the phone as if it never came with that feature in the first place. As for lack of sideloading, we'll see. I heavily rely on NewPipe, but maybe there's another way to scratch that itch.
- usrn 5y agoAll mobile OSes are dogshit.
- rektide 5y agoPalmOS/webos forever! ;) I never actually used it. But I like the idea. And I believe the web platform is a good existential hedge against the undying forever turning-to-crap-iness that so widely defines the trend of everything else. For now web standards still have a lot of good geeks advancing good moral causes and capabilities-- amid some less than excellent causes, yes, but even these make their way through gauntlets of review, through committees.
- usrn 5y ago
- qball 5y ago>normal desktop Xorg Interestingly, webOS actually did let you do this; chrooting into a lightweight desktop environment (the default one offered was LXDE) was as simple as launching the application. Sure, dual-boot configurations were eventually offered, but being able to switch environments and run any (ARM-compatible) Linux software at will had a good chunk of uses, especially in an environment where apps (and the developers to make them) weren't forthcoming.
- rektide 5y agoI bought a OnePlus last summer to go run wayland/sway/web on last summer, but have spent zero time trying to get a debian/debian-ish installed yet. Shame. I also have had some decent tablet-style 2-in-1 computers for half a decade plus, but havent spent hardly any time trying to operate without a mouse+keyboard. For shame! Modern industrial software design is incredibly productive, approachable, consumeable. But what a sick abomination, software that restrains & bounds, platforms that priorotize the platform over the users. I have respect, the maasification & sucess of de-personalized software is epic, has done wonders. But there just being so so few healthy, robust, explorable open ended & personalized/personable alternatives: it makes me beg that the future doesnt just keep closing up/shutting down forever, makes me so want to see some post-desktop opening & sourcing of more.
- car_analogy 5y ago> Unfortunately, these functions are also incredibly useful for malicious apps [..] Google has already limited which apps on Google Play can use the Accessibility API, and in Android 13, they’re taking things one step further by heavily restricting API access for apps that the user has sideloaded from outside of an app store. An API that is so limited that malicious apps cannot abuse it, is too limited to be useful for non-malicious apps. This is just boiling the frog to make sideloading entirely useless, so users need permission from Google for any app they wish to run.
- ars 5y agoThe article explains how what you said is not correct. You do NOT need Google's permission.
- deleted 5y ago[deleted]
- tragictrash 5y agoFrom the article: These restrictions are tied to a new permission in Android 13 called ACCESS_RESTRICTED_SETTINGS. This permission controls whether or not the user can enable an app’s accessibility service. When an app has been sideloaded using the non-session method, ACCESS_RESTRICTED_SETTINGS is first set to “deny”. After viewing the “restricted setting” dialog, ACCESS_RESTRICTED_SETTINGS is set to “ignore.” At this point, the user can go to the app info page for the app in question, tap the three-dot menu, and then tap “allow restricted settings” to unblock access to the accessibility service. The user will then be asked to authenticate themselves, and if they pass, ACCESS_RESTRICTED_SETTINGS will be set to “allow” for the app. The system does not tell the user they can do this, but this could change in future Android 13 builds. Sounds like the accessibility apis are behind another settings screen now.
- interpol_p 5y agoThis is similar to allowing full network access for custom keyboards on iOS. You can't allow it via an easy prompt, you must navigate into settings and explicitly enable it Same for always-on location access. I think this is the right way, users who intend to enable these things should really have to think about it and know what they are doing to allow an app that much access
- kcb 5y ago> For your security, this setting is currently unavailable. That's got to be one of the most Orwellian statements you can make.
- kmeisthax 5y agoMy personal pet peeve is security dialogs that don't explain why permission was denied or how to get permission[0]. Some of the more recent Android lockdown error messages that Google has added to the OS seemed almost laser-focused on pissing me off. Related: some of the scoped-storage changes they pushed through have error messages like "For your privacy, choose another folder" if you try to, say, grant an application access to the Downloads folder. This is stupid for two reasons: 1. There are legitimate reasons for wanting to do this, but no override for those cases 2. The message does not actually explain the privacy risk beyond saying that there is one At least Apple tried to make a user-focused explanation for iOS's security policy. Google just says no in the lowest-effort way possible. [0] Bonus points for UI design that actively hides actions you cannot do, purely to gaslight the user into thinking they don't exist.
- zozbot234 5y agoDo note that the article describes multiple ways that non-Play Store apps may still be allowed to use these API's. For example, this change will not impact apps installed from an F-Droid repo.
- bpye 5y agoI'm not sure what is gained by gating this on the API used though? Couldn't you get around this by having the user install something using the session API which then installs the malicious app that uses the a11y API - it might require convincing the user to click through another install, but I'm not sure how much of a barrier that actually is.
- MishaalRahman 5y ago>Couldn't you get around this by having the user install something using the session API which then installs the malicious app that uses the a11y API - it might require convincing the user to click through another install, but I'm not sure how much of a barrier that actually is. Just a note here, but the restriction isn't "chained". The malicious app using the a11y API itself only needs to be installed via an installer using the session-based API. So a "dropper" app implementing the session-based API could pull the APK for the malicious a11y using app from some source and then ask the user to install it. The malicious app's accessibility service could then be enabled. Yes, this is a loophole, but if Google didn't do this, then you wouldn't be able to enable an app's accessibility service no matter where it was sourced from. And Google's already in hot water with the EU, so I don't think they want to get in trouble for hindering 3P app stores. However, I still think this targeted approach is smart. A lot of apps that users use to download and sideload apps (browsers, mail clients, messaging apps) have no reason to go and implement the session-based installer API, so this restriction would add at least one more barrier to apps gaining a11y access.
- kllrnohj 5y ago> A lot of apps that users use to download and sideload apps (browsers, mail clients, messaging apps) have no reason to go and implement the session-based installer API As the article notes even if those apps do want to use the session-based installer API for some reason, they can just flag that the APK came from either PACKAGE_SOURCE_LOCAL_FILE or PACKAGE_SOURCE_DOWNLOADED_FILE to trigger the same side-load protection behavior. Which, yeah, I don't see why something like eg Firefox would be interested in bypassing this behavior.
- superkuh 5y agoThere is no such thing as side-loading. Installing applications is the default, locked-in walled gardens are the thing we need a term for. e-Prison?
- fartcannon 5y agoSince it's Apple's fav thing, I recommend iPrison.
- deleted 5y ago[deleted]
- selfhoster11 5y agoI recommend "app prison" or a similarly un-nerdy term to get some traction. e-Prison sounds like something the FSF would come up with.
- ars 5y agoFor those who didn't read the article: "Google confirmed to Esper that this restriction was designed to not affect apps installed from app stores, both preloaded (like Google Play) or sideloaded (like F-Droid). This is because the company does not want to restrict accessibility API access for all apps that are sideloaded — they just want to restrict access for apps that came from less legitimate sources."
- IG_Semmelweiss 5y agoHonest question What keeps google from defining f-droid as a "less legitimate source" ?
- ravi-delia 5y agoI mean, nothing? Which means the fact that they specifically carved out an exception for all app repos implies that at least someone at Google is making a good faith effort here. It's still a pointless overreach there should at least be an easy setting for of course, but it seems as though they're trying to strike a balance between protecting the masses and giving power users power.
- MishaalRahman 5y agoRight, in fact, when I was researching for this article, I thought that the fact that the restriction didn't apply when installing apps via the session-based installation API was a loophole/because it wasn't fully implemented in DP2. I surmised that this loophole was intentional so as to not hamper third-party app stores from providing users with apps that use the AccessibilityService API, but I was only able to confirm my suspicion after contacting Google PR.
- kllrnohj 5y ago> It's still a pointless overreach there should at least be an easy setting for of course That seems like a stretch. Why should it be easy to give any app full permission of your device? This is an extremely dangerous permission to give, well, anything. It should be possible (and it seems like it is), but why should it be easy? And calling it a "pointless overreach" is some real sticking your head in the sand stuff. This isn't a fake threat. This abuse isn't theoretical, it's deployed in the wild. The article even provides multiple examples.
- JaimeThompson 5y agoTracking can be much more harmful so when will Google make app developers, including themselves, hop thru this many hoops to protect users?
- new_user_final 5y ago
- causality0 5y agoI wish I could just mail Google a hundred dollar check and a note that says "please don't treat me like a goddamn mouth-breather" and get a permanent "I'm a big boy who wipes my own ass and everything" code for unlocking bootloader and giving root. Sometimes I think it would hurt less to tear the bandage off quick and switch to iOS rather than watching Android slowly get beaten into the Apple mould.
- ev1 5y agoThis exists, just use Pixel?
- Dylan16807 5y agoI don't think Pixels let you keep all the functionality when you unlock the bootloader. Am I wrong?
- bpye 5y agoYou might be thinking of SafetyNet. I'm not sure if there are any reliable ways to get root without tripping SafetyNet, but last I knew you could - on a Pixel - flash a different ROM and then relock the bootloader, and you'd be fine. Things may have changed in the last few years though.
- josephcsible 5y agoYou still fail SafetyNet if you do that.
- aaaaaaaaata 5y agoWhat apps are actually enforcing SafetyNet?
- diggernet 5y agoI wonder if would it be possible for something like εxodus to detect this when they scan an app. I'd love to see a SafetyNet flag in their scan reports.
- causality0 5y agoThe only time an Android "upgrade" has given me a better experience was when I updated a tablet from Android 3 to Android 4. Every other time it's been worse performance and broken workflows.
- wtallis 5y agoI understand the broken workflows thing. But "worse performance" actually sounds a little bit impressive to me (relatively speaking), because it implies you've had multiple Android devices actually get major version upgrades, rather than being abandoned and forcing you to buy a new device to get a newer OS.
- neurostimulant 5y agoSome devices are truly loved by the community and kept alive by people tirelessly adding support for those devices in lineageos. For example, galaxy s4 [1], a phone released on 2013 (Android 4.2 jelly bean), is still supported by lineageos 18 (android 11). [1] https://wiki.lineageos.org/devices/jflteatt/ https://wiki.lineageos.org/devices/jflteatt/
- josephcsible 5y agoBut remember that you still don't get security updates to the OEM's proprietary drivers with custom ROMs.
- deleted 5y ago[deleted]
- usrn 5y agoI'd be tempted to like Android 4 but I think that's when they got rid of the framebuffer requirement for kernels so it meant you had to use Android for graphics and couldn't just replace the userspace with eg debian anymore. EDIT: I've probably used up my quota so here's my reply: Userspace only cares about CPU arc. You can grab a debian rootfs and run it on a kindle/android/rasbpi etc. without even having to recompile things. The kernel however needs drivers and with modern Android many of them have to be rewritten. Replacing the kernel is a development exercise while replacing the userspace is mostly a matter of just installing the right software.
- deleted 5y ago[deleted]
- lordofgibbons 5y agoCan we as a hacker community say enough is enough and put our collective efforts into making something like PureOS a viable option for daily use? PureOS currently suffers from a tragedy of the commons. I, like many others am afraid of investing a lot of my time into developing for it for fear that not many others will adopt it and my efforts will be wasted. How can we build/market PureOS as a credible alternative for other app developers to start building on top of it? *Edit It doesn't have to be PureOS - that was just an example. It could be Sailfish OS, or Plasma Mobile. We just have to pick one to create a self-sustaining ecosystem around.
- MomoXenosaga 5y agoYou can't. Microsoft, Samsung, Huawei- they all tried. Understandably because nobody wants more work.
- oorza 5y ago> How can we build/market PureOS as a credible alternative for other app developers to start building on top of it? Start by convincing paying customers that cyber security and/or their privacy are important.
- josephcsible 5y agoOne major hurdle is getting the existing app developers to stop intentionally hindering efforts to make their apps work through compatibility layers.
- lordofgibbons 5y agoCan you expand more on this? Are they deliberately trying to detect compatibility layers?
- josephcsible 5y agoModern phones have chips that can do hardware attestation that they're running an OS that's been blessed by Google. A lot of apps, e.g., McDonald's and most banks, will refuse to run if this attestation fails.
- xdxfw 5y agoRooting becomes a no brainer - message sent from rooted lineageos poco x3 pro
- selfhoster11 5y agoHelp, I can't access my banking app! - sent from every device with SafetyNet invalidated. I'm not trying to be sarcastic, just pointing out the reality of the situation and the reason why I didn't root or mod my own phone.
- neurostimulant 5y agoYou can install 3rd party roms but skip the rooting part to not mess with SafetyNet.
- josephcsible 5y agoThat still breaks SafetyNet, because it checks if the bootloader is unlocked, which it has to be to install a custom ROM.
- deleted 5y ago[deleted]
- aappleby 5y ago...did anyone here read the actual article?
- yjftsjthsd-h 5y agoUnless I missed something, the article basically says what the headline says. There's some nuance, but "you can currently work around this by jumping through some major hoops" doesn't really change much IMO.
- KerrAvon 5y ago@dang or other moderators, could you please kindly fix the headline? The correct headline is: > Android 13’s new sideloading restriction makes it harder for malware to abuse Accessibility APIs Seems a lot less inflammatory. edited for politeness
- josephcsible 5y agoThat's too long, or I would have submitted it like that.
- baisq 5y agoGod, Android 13 is fugly. It's as if they've taken the worst of iOS and the worst of MIUI and merged it.