122 karma · joined February 25, 2022
> True, depends on the phone though, some of them cannot be locked again and there's no way to completely fix those phones with a better ROM.
Then you shouldn‘t use those phones for a secure setup. I think we can agree on that. But the author of the article used a phone that is capable of locking the bootloader with alternate ROMs.
If you assume this to be correct, then there's no point in attempting to make your phone private. Privacy isn't possible without security.
> None of that matters if your data is just sent to Google anyways.
when you use a custom ROM, that's not necessarily true. But using a custom ROM doesn't necessarily mean you have to permanently unlock your bootloader, so that argument doesn't make sense.
Verified boot doesn't prevent you cleaning up the device. Modern android phones have wonderfully sophisticated per-file disk encryption.
In pixels, the decryption key is stored in a secure enclave (Titan M). If you want to wipe the device safely, you can just reset the OS. (This deletes the decryption key from the secure enclave which turns all user data on the user data partition into random junk).
GrapheneOS for example gets all of these things right. It is possible to make your phone secure, but not by permanently unlocking the bootloader and rooting the device.
Additionally, the updates that the forked OS provides don't include firmware updates for essential parts like the modem (this is also the reason why phone updates are not available in the first place). So it's essentially a security theatre.
Firefox doesn't use per-site isolation, doesn't use process sandboxing and - on top of that has a JIT, so there's W^X violations. Normal app sandboxing via Android permissions is not sufficient for something as complex as a browser. The potential for possible exploits inherently is massive. Other browsers (chromium-based) like Vanadium have very sophisticated sandboxing, so there's no reason to use something inferior.
Traffic over tor is good, but shouldn't be used with authenticated services, as it deanonymizes your connection. Instead, it should only be used for specific (unauthenticated) actions, like browsing news.
In doing so, it also disables integrity checks, thus making persistence (even without rollback) a lot easier for a potential attacker.
So your phone becomes a lot more vulnerable to all kinds of attacks, not just physical ones.
See also: the Android Documentation for verified boot (https://source.android.com/docs/security/features/verifiedbo...)
For example, if you block facebook with a firewall, it can still send an intent to the download manager to make network connections.
(see https://madaidans-insecurities.github.io/android.html#firewa...)
(https://madaidans-insecurities.github.io/firefox-chromium.ht...)
- you unlocked your bootloader w/o re-locking it again → insecure
- you used a phone that doesn‘t receive OEM updates anymore → insecure
- you use firefox over tor: no sandbox, very unique fingerprint
- all of the device‘s traffic is routed over tor → any authentication on a non-privacy service compromises your anonymity
I don‘t think this is a good setup.
Also, rust forces you to actually model the complexity of the real world. I think the best example for this are the various string types. There is one for Interop with C, one for Paths, one that is utf-8 etc. Your code explicitly states what to do with edge cases. Edge cases that existed anyway but are now visible.
Don't get me wrong, I don't dislike Rust. It's an awesome language.
I'm just saying that for most people it's a bad idea, especially regarding Linux. Linux's security is abysmal because the desktop security model is fundamentally flawed.
Take Flatpak for example. While it is a big step forward in terms of portability, ease of use and security, it is still allows applications to pick their permissions themselves. Even dangerous ones like X11 display server access, full file system access or camera access.
However, there already is a number of secure open source alternative mobile OSes based on Android, GrapheneOS for example.
Also, driver blobs for modems are often out-of-date and insecure. Making the phone drivers fully open source will probably not happen.
If you know what you’re doing, installing a different OS onto can be liberating and good for the environment – most of the time the hardware is perfectly fine, just the software becomes more bloated and slower as the device ages. It’s just - in my opinion - more risky.
Speaking of side projects, I recently built my own side project builder at just-kidding.org ;)