Live data from Hacker News

Android may soon restrict on-device ADB

kitsumed.github.io

131–140 of 535 posts

Re: Android may soon restrict on-device ADB

#131
It's this stuff thats caused me to start degoogling as much as I can. I've started using nongmail emails and removing photos.

I Don't know what else I can do though, next up is switching to grapheneOS but I'm a ways off from that for now.

Re: Android may soon restrict on-device ADB

#133
Can they ruin it faster i am sick of it already. Need to root the phone to get basic functionality, i need like 6-7 magisk modules to do basic things. I can't access file system on device i paid 250$. I have to use adb to change basic things, i rather use symbian.

Re: Android may soon restrict on-device ADB

#134
post #124

Earlier quoted context omitted.

Ok, that makes more sense. Hooray for stuff getting even worse...

Remote attestation itself being a questionable idea at best, so it's bad things creating a market for even worse workarounds.

No objection there.

Also telling that advertising and locking down devices are driven by the same companies...

Re: Android may soon restrict on-device ADB

#136

Can they ruin it faster i am sick of it already. Need to root the phone to get basic functionality, i need like 6-7 magisk modules to do basic things. I can't access file system on device i paid 250$. I have to use adb to change basic things, i rather use symbian.

Symbian pioneered this bullshit. Having to sign apps with Nokia keys just to install them was a thing since the days of S60. And it all went downhill from there.

Re: Android may soon restrict on-device ADB

#137
post #40

I am generally in favor of security improvements, but I do not really see much of a benefit here. This attack vector requires both that the user enabled developer settings and that they have remote adb enabled. So, this does not seem to be a realistic attack vector for 99.9% of the users and most of the other 0.1% probably know what they are doing. The other proposed change (to restrict access to certain interfaces o…

Isn't this because of the kimwolf (and now 6+ other botnets) that are taking advantage of people running residential proxyware unknowingly on the device which permits outbound connections to 127.0.0.1 on tcp/5555 to auth in and exec wgets or drops a loader that grabs the ddos malware APKs and install it?

You haven't been able to connect to an android device on port 5555 for yeeears. Every time you enable adb/IP it generates a new random port, or you need to use the QR/PIN pairing thing. On top of needing to enable developer options, adb/IP, confirm the fingerprint.

Re: Android may soon restrict on-device ADB

#138
post #18

> Spamming the thread will only cause Google developers to lock the issue, ignore valuable community feedback, or stop sharing public updates about this change entirely. So nothing would change (they can also lock away your "valuable community feedback" because what bothers them is the criticism itself), thus feel free to express your approval

> because what bothers them is the criticism itself

I think there's a difference between criticism of a policy and being brigaded by a reddit mob.

Re: Android may soon restrict on-device ADB

#139
post #77

Earlier quoted context omitted.

We used to call programs like this, that allow someone to remotely break your system, a Trojan horse...

and now people install Remote Access Trojans just to let GPT and Claude think and work for them, granting them shell and a11y access. really? after seeing that, nothing surprises me

Yes, really. The obvious answer that security maximallists deny even exists is, who is doing it and why. In LLM case, users are doing it themselves to allow a way of computing they want and find useful, in spite of platform locks designed to deny users just that.
Post reply on HN