3 ms·
> Third parties, both companies and FOSS types, are doing better at protecting Android than Google. I'm working on a 3rd-party OSS project securing Android htt
by dmix 11y ago
> Third parties, both companies and FOSS types, are doing better at protecting Android than Google.
I'm working on a 3rd-party OSS project securing Android https://copperhead.co/android https://copperhead.co/android (/shameless self plug)
While Android is in pretty bad shape, I'd still give Google some credit, they have been slowly starting to improve their OS security in the last 2 years. But quite a few early design choices favouring performance over security, such as Zygote rendering ASLR ineffective, are lingering and holding back Android's security.
They are also using Linux kernels from 2012 or earlier (3.4) on almost all devices, although from what I've heard that is mostly the fault of vendors such as Qualcomm moving slowly.
- kllrnohj 11y agoBad shape? How so? Zygote is more about memory than performance, and that's still a needed thing. SELinux is in enforcing mode and has an increasingly tighter and tighter net. Also Google is using 3.10 on the devices they sell, not 3.4. What Samsung, HTC, etc... ship is a different story, but that's not under Google's control.
- dmix 11y ago> Zygote is more about memory than performance Memory = performance. We disabled Zygote and performance took a hit (ie, apps start slower because classes aren't preloaded). > Google is using 3.10 on the devices they sell, not 3.4. 3.10 is on some new devices such as Nexus 9, including Lollipop upgrades for Samsung S6 and HTC M9. Google Nexus 5/7 is 3.4. So basically <=3.4 is on 99.99% of Android devices...
- nickpsecurity 11y agoGood for you. We Android users appreciate people picking up Google's slack. :) It looks like your people are mixing the regular hardening advice with some ported stuff from BSD/Linux security work. This is low-medium in that it won't stop serious attackers if you get popular. Yet, even baking in the basic hardening by default should reduce risk of many real-world attacks. The other stuff might do more in final form. Keep at it.
- dmix 11y agoHaving read a few of your other comments I'd be curious to hear your thoughts on ways in which we could harden Android (on here or via email). Our focus now is indeed adding memory protections to the underlying OS, to get Android up to date with at least 2004-era exploit mitigation. Before moving on to higher-level stuff :)
- nickpsecurity 11y agoLinux is so inherently insecure that it's hard to say without processor & toolchain modifications. What you can do is follow lead of the others: combine a microkernel (eg OKL4, OC.L4) with paravirtualized Android with security-critical components running outside of Android. The Nizza Architecture [1] below illustrates this. A better, but commercial, approach [2] shows how to handle drivers and some other things better. It's been deployed in a ridiculous number of phones with success. So, standardize on a phone, audit/test the crap out of the drivers, put an OKL4/Nizza-style architecture on it, and pull out anything security-critical to run on microkernel with careful input validation & state management. Should reduce TCB, increase reliability, and prevent spoofing if you fully implement Nitpicker for mobile. Hope that helps. Quick note: be sure to clear all internal registers and cache if kernel transitions from trusted software to untrusted software if you're worried about covert channels (esp key leaking). Both of those can leak keys to professionals if they compromised the Android portion. [1] http://os.inf.tu-dresden.de/papers_ps/nizza.pdf http://os.inf.tu-dresden.de/papers_ps/nizza.pdf [2] http://www.eit.lth.se/fileadmin/eit/project/142/virtApproaches.pdf http://www.eit.lth.se/fileadmin/eit/project/142/virtApproach...