I quote boosted this before focusing on the 24h delay, but the worst part is having to enable developer options.
-
RE: https://chaos.social/@grote/116257002625921666
I quote boosted this before focusing on the 24h delay, but the worst part is having to enable developer options.
Fairphone: Settings -> About phone -> Build number (7 taps)
Samsung: Settings -> About phone -> Software information -> Build number (7 taps)Given the steps differ per device it is impossible for any third party app store to give clear instructions. To top it off, the first 3 taps give *no feedback* at all.
Even worse, some apps refuse to run on devices with dev mode enabled.
-
RE: https://chaos.social/@grote/116257002625921666
I quote boosted this before focusing on the 24h delay, but the worst part is having to enable developer options.
Fairphone: Settings -> About phone -> Build number (7 taps)
Samsung: Settings -> About phone -> Software information -> Build number (7 taps)Given the steps differ per device it is impossible for any third party app store to give clear instructions. To top it off, the first 3 taps give *no feedback* at all.
Even worse, some apps refuse to run on devices with dev mode enabled.
Google obviously knows how user unfriendly it is to enable developer mode and how this will effectively make it impossible for the vast majority of non-technical users to access any third party app stores. This is as malicious as malicious compliance to EU law goes. I cannot think of a more aggressive roadblock they could have put up, even forcing some to choose between third party app stores like #FDroid or #IzzyOnDroid and banking apps.
There is no doubt about it, this is not about safety.
-
Google obviously knows how user unfriendly it is to enable developer mode and how this will effectively make it impossible for the vast majority of non-technical users to access any third party app stores. This is as malicious as malicious compliance to EU law goes. I cannot think of a more aggressive roadblock they could have put up, even forcing some to choose between third party app stores like #FDroid or #IzzyOnDroid and banking apps.
There is no doubt about it, this is not about safety.
Keep in mind, enabling developer mode is just *ONE* of the many steps. This whole process is made as difficult and with as much friction as they possibly could. No third party app store could guide most users through this successfully.
-
Google obviously knows how user unfriendly it is to enable developer mode and how this will effectively make it impossible for the vast majority of non-technical users to access any third party app stores. This is as malicious as malicious compliance to EU law goes. I cannot think of a more aggressive roadblock they could have put up, even forcing some to choose between third party app stores like #FDroid or #IzzyOnDroid and banking apps.
There is no doubt about it, this is not about safety.
@SylvieLorxu They surely know. Its called "developer mode" for good reasons; it shouldn't be used in normal occasions.
Them putting any feature behind this mode is a clear sign they don't regard it as a feature that should be used at all.
-
@SylvieLorxu They surely know. Its called "developer mode" for good reasons; it shouldn't be used in normal occasions.
Them putting any feature behind this mode is a clear sign they don't regard it as a feature that should be used at all.
@odd @SylvieLorxu Not to mention the decade long backlog of websites saying "if somebody tells you to activate developer mode to install software they're being dishonest" because that used to be true, and you'll have people and LLMs giving bad advice in that regard for the next decade at least.
-
Keep in mind, enabling developer mode is just *ONE* of the many steps. This whole process is made as difficult and with as much friction as they possibly could. No third party app store could guide most users through this successfully.
@SylvieLorxu And there I thought developer mode was discouraged for "standard users":
"Developer modes expose features of the mobile operating system (MOS) that are not available during standard operation. An adversary may leverage a vulnerability inherent in a developer mode to compromise the confidentiality, integrity, and availability of DOD sensitive information. Disabling developer modes mitigates this risk."
(Tenable Audit: https://www.tenable.com/audits/items/DISA_STIG_Google_Android_15_COBO_v1r2-AirWatch.audit:3722d2c6e738b1955d48f57783163430)
So, this is about security? LMAO…
-
@odd @SylvieLorxu Not to mention the decade long backlog of websites saying "if somebody tells you to activate developer mode to install software they're being dishonest" because that used to be true, and you'll have people and LLMs giving bad advice in that regard for the next decade at least.
@dascandy @odd @SylvieLorxu THAT shit is already happening. I was standing next to a person trying to get their phone's storage (connected via USB) to show up on a PC, which it didn't. They asked their favorite LLM for advice, which tried to guide them through enabling developer mode – as first advice! (hint: a simple reboot of the phone solved the issue).
-
R relay@relay.infosec.exchange shared this topic
-
@SylvieLorxu And there I thought developer mode was discouraged for "standard users":
"Developer modes expose features of the mobile operating system (MOS) that are not available during standard operation. An adversary may leverage a vulnerability inherent in a developer mode to compromise the confidentiality, integrity, and availability of DOD sensitive information. Disabling developer modes mitigates this risk."
(Tenable Audit: https://www.tenable.com/audits/items/DISA_STIG_Google_Android_15_COBO_v1r2-AirWatch.audit:3722d2c6e738b1955d48f57783163430)
So, this is about security? LMAO…
@IzzyOnDroid @SylvieLorxu Oh, so I wasn't too paranoid by disabling developper settings when they're not needed. It's quite obvious when presented like that, but I wasn't aware that it changed how the operating system works (I thought it only exposed sensitive options).
Thanks for pointing it out!
