Speaking off, I’m still having issues adding it, since it still get confused by the k9 original repo origin, even if i try to filter the pre-release .apk’s with the thunderbird name.
My bad, still kept the k9-mail repo instead of the thunderbird fork.
Yep, and Google own employees are forbidden to protest of that project, if they wish to keep their job.
Excuse me, what. What is your reasoning behind that question ?
You can. It just show you everything that need additional info. You can just choose to move the map to the shop you want to edit hours and do that. You can also filter the StreetComplete missions in the settings if you want to only update business hours and description.
Spotify Lite for you, and me.
And even that advantage can be minimized by getting any bundle of privacy products, like Proton which offer all of those (Mail, VPN, Drive, Calendar) or even with your self-hosted VPS (Some VPS seller even allow you to prepare it with Nextcloud and a VPN relay for near no extra paiement).
I see the “pay once to one company”, but you also need to trust them entirely, for EVERYTHING.
Also, there’s already plenty of companies doing such thing (regardless of how practical/private/secure they are)
Just higher standards.
Thanks for the tip ! To be fair, I haven’t even checked the result and missed on it.
It still create an attack vector, as it allows a potential extra method to get access to it, in addition of potential hardware exploits that i shared to gain root. Yes, you can minimize the risks correctly, but the user is the only real barrier against it, not the software anymore. The less potential way to exploit your phone, the better it is. You shouldn’t rely on thinking that such feature is fully attack-proof.
Stop it [send] Mom [send] This is [send] your warning [send] ⚠️ [send] … [send] Did you even read Mom ? [sent 53 photos]
Aggree with common sense, but more difficult to establish with some people.
The actual Magisk prompt that ask you if you want to give root to such app. This UI layer.
Although, i suppose it could be countered by explicitly refusing all requests or enabling a biometric confirmation
Just logical. If you gain the privilege to modify system bits, then it just open the potential for attacks abusing root access. And it has been done already. You are just removing one step for them. https://www.bleepingcomputer.com/news/security/loki-trojan-infects-android-libraries-and-system-process-to-get-root-privileges/ https://www.bleepingcomputer.com/news/security/highly-advanced-spydealer-malware-can-root-one-in-four-android-devices/ https://www.bleepingcomputer.com/news/security/new-abstractemu-malware-roots-android-devices-evades-detection/ https://promon.co/security-news/fjordphantom-android-malware/
Only big manufacturers can really pay to control entirely the hardware inside it, and allow you to modify it. Checkout Fairphone for example. They’ve been forced to stop hardware security updates due to their chip manufacturer, who refused to continue supporting it, despite them trying to support their devices for plenty more years. This explains the choice with Google.
Sadly, can’t be re-locked. Would have loved to get a Motorola if it was.
That’s the main issue really, as it open the possibility to manage your device for anyone getting hold of it. Probably some debug attack methods also with it.
Proove us that you can get better security while remaining able to be fully modified with other phones and brands. https://www.privacyguides.org/en/android/#divestos
If you have the UI layer able to grant root access, it has root access itself and is not sandboxed. If the UI layer can grant it, an attacker gaining slight control over it has root access. An accessibility service trivially has root access. A keyboard can probably get root access, and so on. Instead of a tiny little portion of the OS having root access, a massive portion of it does.
In the verified boot threat model, an attacker controls persistent state. If you have persistent root access as a possibility then verified boot doesn’t work since persistent state is entirely trusted.
A userdebug build of AOSP or GrapheneOS has a su binary and an adb root command providing root access via the Android Debug Bridge via physical access using USB. This does still significantly reduce security, particularly since ADB has a network mode that can be enabled. Most of the security model is still intact. This is not what people are referring to when they talk about rooting on Android, they are referring to granting root access to apps via the UI not using it via a shell.
Beat the main purpose of GrapheneOS. Open the phone to a broad lot of security issues.
Indeed. YACB : Yet Another Call Blocker and SAI : Should I Answer
Actually, you were right. The issue for me is that the original k9-mail repo did also released the current beta thunderbird version (and i think, one with still the k9 branding if needed). I was trying to switch to it via that repo, and didn’t noticed the thunderbird fork listed the in the repo. There’s no changes, outside of the releases only being thunderbird branded outside of all the previous k9-mail ones. If you were on k-9 mail, and want to switch to it on Obtainium, manually install the new version and mugrate your settings to it. And once it’s all done, remove the k9-mail repo from Obtainium, and add that thunderbird one.