<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: 3xpltr3</title><link>https://news.ycombinator.com/user?id=3xpltr3</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 25 Jul 2026 23:42:32 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=3xpltr3" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by 3xpltr3 in "Android May Soon Restrict On-Device ADB"]]></title><description><![CDATA[
<p>I agree with user TeMPOraL in his comment. Those who aren't trapped in tunnel-vision, know the app permissions themselves have ALOT of access to all data on your device and users give the apps these permissions. Should we say that every app is a CVE? 
The real reason any Google dev wants ADB gone is to close open source and lock down the OS to Google sign-ins and a proxy proprietary closed source eco-system. ADB is the master-key to rooting Android devices, getting Android shell access to /root, uploading *.apks, etc... But for the Google monopoly, it makes sense to them to close/restrict this access, then funnel all requests for it through Google's identity gateway for access. So the argument "this app can bypass OS security through ADB and is therefore a CVE"  is not valid and an foolish from its /root.</p>
]]></description><pubDate>Sat, 25 Jul 2026 15:17:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=49048269</link><dc:creator>3xpltr3</dc:creator><comments>https://news.ycombinator.com/item?id=49048269</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49048269</guid></item></channel></rss>