71–80 of 80 posts
This is interesting. I thought granting internet access to apps is not avoidable on Android. When an app does not request internet, is it really guaranteed that it cannot talk to the outside world? Or is it having other avenues like opening a browser or some other component with a custom url or something? Update: I just asked Gemini, and it does not look good: An Android app without the INTERNET permission is not gua…
This is interesting. I thought granting internet access to apps is not avoidable on Android. When an app does not request internet, is it really guaranteed that it cannot talk to the outside world? Or is it having other avenues like opening a browser or some other component with a custom url or something? Update: I just asked Gemini, and it does not look good: An Android app without the INTERNET permission is not gua…
"I just asked Gemini, and it turns out that Mossad can steal my data anyways". - An app without the INTERNET permission will crash the moment you try to access the internet. It's like a rite of passage of every android developer with every new project, you forgot the permission. - Launching an Intent is EXTREMELY visible. It opens a full on browser. It's limited to a GET with a dedicated URL, so what are they going t…
Earlier quoted context omitted.
I use a rooted phone and afwall+ which uses the underlying Linux firewall. There's also the mobile and WiFi data permissions you can change manually.
How is the rooted experience these days? Do you deal with broken (banking) apps all the time?
For me, root on my own devices is a matter of principle. If an app doesn't work, then I don't want it. In the future I might carry a gimped android device for essential things like train apps if I have to, but then it won't be the device I actually carry in my pocket, it'll be in my bag. Mobile computing is for me.
Earlier quoted context omitted.
> If two apps from the same developer share a User ID (sharedUserId), they run in the same process and share all permissions Good grief. What a huge vulnerability. Is there some benefit that justifies this?
First, `sharedUserId` is opt-in. You need something like that for plugin / extension like system. Third, it is being deprecated. and people are screaming "bad google" "android is no longer free!"
By the user?
> You need something like that for plugin / extension like system.
Plugin/extension != app.
How does this work? I was under the impression that newer android sdk versions required permissions to access the filesystem... if you're using an older sdk, I can't really imagine the app working for longer than a year.
This is from the Android documentation[1]:
"Because the user is involved in selecting the files or directories that your app can access, this mechanism doesn't require any system permissions […]"
[1] https://developer.android.com/training/data-storage/shared/d...
How does this work? I was under the impression that newer android sdk versions required permissions to access the filesystem... if you're using an older sdk, I can't really imagine the app working for longer than a year.
It's explained in the readme. Granting access to folders on the file system is a process independent from permissions. This is from the Android documentation[1]: "Because the user is involved in selecting the files or directories that your app can access, this mechanism doesn't require any system permissions […]" [1] https://developer.android.com/training/data-storage/shared/d...
Two things I really like: 1. Markdown loads as preview 2. Plain text files wrap instead of scrolling to the right Good job and thank you for sharing
Earlier quoted context omitted.
Why would rendering a document need internet access?
PDFs can do all sorts of shenanigans, such as bundle executable javascript that runs when the file is opened.