11 ms·
Hardening the Kernel in Android Oreo
- pjmlp 9y agoNice set of features, that the majority of Android users will only get in a few years. Maybe we should start making bets if Android Oreo be able to beat Nougat and be above 13.5% next year this time around.
- limeblack 9y agoYou probably know this but because of project Treble for future versions after Android Oreo will probably be adopted more quickly. It is unlikely for Oreo to do much better then Nougat then from what I have read.
- pjmlp 9y agoAnyone beliveing that project Treble will change anything should listen to the ADB Podcast about it. http://androidbackstage.blogspot.de/2017/08/episode-75-project-treble-for-hal-of-it.html http://androidbackstage.blogspot.de/2017/08/episode-75-proje... Key points: 1 - Google will keep on allowing OEMs to customize Android 2 - OEMs will keep being responsible for delivering updates 3 - OEMs are advised to push fixes upstream and provide updates Given that they are just advised, and not required to act accordingly, do you want to bet how many will provide Treble updates instead of selling new handsets?
- limeblack 9y agoThat's not what this top comment says https://news.ycombinator.com/item?id=15066729 https://news.ycombinator.com/item?id=15066729 at least that's how I interpreted it.
- pjmlp 9y agoListen to the podcast.
- sigmar 9y agoYou are dead on. The problem is incentives. There is no technical solution to solve the issue of OEMs not wanting to spend time/resources on updating older phones. Treble will help out LineageOS, CopperheadOS, and XDA devs. But it won't improve the update cycles for OEMs when their business (ie profit aims) pressures them to limit development resources to new phones.
- bingobob 9y agobut wouldn't treble allow for there custom Android to be updated across there fleet of devices where currently each product has to get its custom build with drivers etc.
- limeblack 9y agoYes this is how I interpreted it but I'm sure the other people here probably know much more which leads me to believe that must not be the case.
- haikuginger 9y agoWhich iteration of "project that will definitely reduce Android device fragmentation and ensure that all capable devices will get the new software version as soon as possible" are we on at this point?
- zanny 9y agoIs it the one where vendors are upstreaming their drivers to Linux mainline, properly supporting them in tree, and users are able to audit and trust their phones for the first time ever? Because that is the actual answer. Everything else is a compromise trying to please vendors who are only trying to exploit users for profit through planned obsolescence and withholding knowledge of how their devices work.
- limeblack 9y agoGlad we are making it more secure. On a side note I love that we now have https://googleblog.blogspot.com/index.html https://googleblog.blogspot.com/index.html http://blog.google http://blog.google and https://android-developers.googleblog.com/ https://android-developers.googleblog.com/ and https://googleblog.blogspot.com/ https://googleblog.blogspot.com/ (which redirects to blog.google without index.html because it appears to be the new site) which is slightly weird.
- mcintyre1994 9y agoOnly one of those works for me (the top one), which amusingly redirects to blog.google which you missed :)
- limeblack 9y agoTry it now it appears index.html isn't optional which frankly is even more confusing.
- mcintyre1994 9y agoTop one works now (by which I mean doesn't redirect to what I think is the actual Google blog now...) :)
- Pharaoh2 9y agoDid you mean https://www.blog.google/ https://www.blog.google/?
- khc 9y ago"Android 8.0 makes KASLR available in Android kernels 4.4 and newer." And yet on my pixel with Android 8.0, I am only using 3.18.52. Who actually ships Android with kernel 4.x?
- trthomps 9y agoI also have 3.18 on my Pixel XL. I assume the unreleased Pixel 2 devices will be running kernel 4.4 if that's what they targeted. They probably wanted to back port it to 3.18 but it was too much work. I'm pretty disappointed they didn't move the Pixel forward to a new kernel though, this seems to be one of the biggest issues with Android.
- pjmlp 9y agoQuite disappointing, yet another bad example for OEMs.
- khc 9y agoI hope so, but given that 3.18 was released almost three years ago I am not holding my breath.
- wmf 9y agoThis is an interesting case study in development cycles. The Pixel XL from October 2016 uses the Snapdragon 82x released in July 2016 but first announced in March 2015 and it uses a kernel from 2014 which gives us a hint about when driver development started.
- MBCook 9y agoI was surprised to read that in the article. New android phones from top vendors (not the $50 junk devices) ship with 3.x kernels? Wow.
- fooker 9y ago3.x kernels with security patches. What seems to be the issue? You can claim big rewards from Google if you report kernel exploits in Android.
- nsxwolf 9y agoDid they have to license the name?
- limeblack 9y agoAssuming you are referring to the name Oreo read this. https://android.stackexchange.com/q/181818 https://android.stackexchange.com/q/181818 EDTI: Fixed so they didn't pay as stated above but I guess it is technically still licensed.
- khc 9y agothe link says they didn't pay, not that they didn't license the name
- X86BSD 9y agoMy understanding was you can use a trademarked name but only if it was in an unrelated category. Clearly no one will confuse a phone running Oreo with a cookie you eat and dip in milk. now if google made a cookie and called it oreo, they would get sued. But IANAL and am probably totally wrong here.
- acdx 9y agoGoogle extremely obviously did not use the name Oreo without asking for permission
- KGIII 9y agoFrom the last time this was asked, they asked permission. With KitKat, they paid - someone linked a citation for it but it's not in my history.
- snorlaxle 9y agoWhat I read at the time is that no money was paid to anyone. Hope you find the linked citation https://techcrunch.com/2013/09/03/google-strikes-bizarre-licensing-deal-with-nestle-to-name-next-android-kit-kat/ https://techcrunch.com/2013/09/03/google-strikes-bizarre-lic...
- MBCook 9y agoGreat to see Google linking to the LWN articles on these features. I always like to see LWN get noticed for their fantastic kernel work. It's the primary reason I've been a subscriber since they introduced subscriptions all those years ago.
- mrhigat4 9y agoAndroid should really use a modern kernel. All the forking mess involved in Android updates is a terrible problem predicated by the lack of generic drivers on mobile devices. Copperhead[0] has been working to apply security patches to the kernel for some time and PostMarketOS[1] has an eventual goal of using the mainline upstream kernel. Really pulling for PMOS. [0]: https://copperhead.co/android/ https://copperhead.co/android/ [1]: https://www.postmarketos.org/ https://www.postmarketos.org/
- kelnos 9y agoYes, this was my first thought as I was reading the article. A better title for it would be "Backporting Modern Linux Kernel Features to Our Really Old Kernels Instead of Doing the Right Thing and Keeping Up To Date". I do -- I really do -- appreciate that version churn is difficult, and the Linux kernel also doesn't make it easy since they don't guarantee any stable internal APIs, but they're also adding a lot of work on themselves by having to maintain their own kernel trees that diverge significantly from mainline. They're also at the mercy (to some extent) of many chipset manufacturers and whatever they've chosen to base their efforts on. A quick look at some kernel release timeframes from the versions they mention in the article: 4.3 - 11/2015 4.4 - 02/2016 4.6 - 05/2016 4.8 - 10/2016 4.10 - 02/2017 The only kernel out of that list I'd unquestioningly accept as it being unrealistic to upgrade to for Oreo is 4.10. 4.8 might be a stretch since I'm guessing they'd already branched internally for Oreo by then, though they likely had a month or so of RCs that they could have used as a base before that. There's certainly risk to basing your work on a newly-released (or soon-to-be-released) kernel, but given the general high quality of kernel releases, I imagine that'd be pretty far down on their list of risks. Regardless, 4.6 or 4.7 would be entirely reasonable to use as a base, and since they own the conformance test criteria, they could also require that all their vendors use that as a minimum version. And yet, they are backporting some features as far back as 3.18, which was originally released in December of 2014, and, while it was designated a LTS kernel, it, at this point in time, has moved into end-of-life status. And we wonder why Android security is a nightmare.
- c2h5oh 9y agoMain reason is that there is a lot of hardware that never got binary blobs / drivers updated for newer kernels. We're talking input controllers, wifi, bluetooth, nfc chips, gyroscopes, amps and half a dozen other parts that never attempted to have drivers mainlined in Linux kernel. It's a chicken and egg problem - they won't make updated blobs until Android doesn't include newer kernel. Android won't use newer kernel because that would block 2/3 of the phones from being upgraded because of Broadcom bluetooth chips alone - Samsung might decide they are better off forking Android than waiting for Broadcom. Edit: Sony has a bunch of phones that can run on 4.4 kernel: https://developer.sonymobile.com/open-devices/ https://developer.sonymobile.com/open-devices/
- bhhaskin 9y agoI really wish Ubuntu touch was more complete. I would switch in a heart beat.
- duskwuff 9y agoDon't hold your breath. The project was effectively cancelled in April. There's theoretically a "UBPorts" project that may continue development, but, without any sort of company backing it anymore, I doubt that it's going to have much of an impact. https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cloud-and-iot-rather-than-phone-and-convergence/ https://insights.ubuntu.com/2017/04/05/growing-ubuntu-for-cl...
- petecox 9y ago'theoretically?' It's happening, albeit without a corporation behind it. They have a weekly youtube vodcast, if you're curious, and a Patreon page with a couple of hundred subscribers.
- srcmap 9y agoI like to see Android add System GUI to monitor: * all apps (including daemon processes) that makes internet connections. * Where they are connecting to. * AND give user to GUI/Options block those connections. I also want Android give users option to audit/monitor all new programs, .so, files that has been added to the systems and by which program, time. If there are suspicious file that is added to the system, we can audit/monitor/report/google where it comes from. In Windows 10, I use netstat to monitor all TCP connections and get the name of the programs and configure the windows firewall to only allow Windows Firewall/Firefox and Chrome to access internet and block IE/Edge/svchost/SearchUI and countless other SW from access internet. My system is so much faster and stable, after I did this.
- limeblack 9y agoThis can be done with apps already although you have to start them on reboot in my experience. Let me go fine the name. It is called NoRoot Firewall.
- FuckOffNeemo 9y agoThis is great, never knew of this before now. Thank you.
- pwg 9y agoAnother one (at least for the 'monitor' portion) is Net Monitor (https://f-droid.org/packages/org.secuso.privacyfriendlynetmonitor/ https://f-droid.org/packages/org.secuso.privacyfriendlynetmo...) which is available in F-Droid (https://f-droid.org/ https://f-droid.org/).
- duskwuff 9y agoI'm not sure I see what security value these features would add for ordinary users. On a modern device, most application processes will be making some sort of network connections, and many of those connections will be to IPs that can't easily be identified, even by an experienced user. (For instance, a lot of those addresses are likely to belong to Cloudflare or other CDN providers.) You can't rationally expect users to make intelligent decisions about whether to allow or block those connections. IMO, it shouldn't be possible at all for applications to run code that's created/downloaded at runtime. iOS has the right approach here. This makes monitoring those files unnecessary -- the only path for code to enter the system is through installing or updating apps.
- dikaiosune 9y agoGlad to see improvements are coming! Articles like this make me more and more curious whether Fuchsia is an alternative bid to resolve relevant kernel vulnerabilities in a more centralized, architecturally driven fashion, not just a way to get out from under the GPL.
- _pmf_ 9y agoSwitching to Fuchsia (which will never happen because it is a toy project to occupy bored engineers) does not magically solve the problem that device vendors want to minimize the work in maintaining their drivers. Even enforcing open source drivers (for the sake of discussion) will not help, because at a certain complexity, the device driver writer requires knowledge about undocumented internals of the device that is just not available outside the manufacturer. There must be an economic incentive for device manufacturers to maintain/update their drivers, otherwise it cannot happen. Users want to buy new devices, not pay directly or indirectly for updating their old devices; this basically seals the deal.
- afsina 9y agoToy project? I doubt that. There is frantic work going on by perhaps more than a hundred engineers if I am not mistaken: https://fuchsia-review.googlesource.com/ https://fuchsia-review.googlesource.com/
- tptacek 9y agoFor similar content but in much greater depth, this is a pretty excellent series of blog posts: https://outflux.net/blog/archives/2017/07/10/security-things-in-linux-v4-12/ https://outflux.net/blog/archives/2017/07/10/security-things...
- nur0n 9y agocan you recommend any other blogs like this?
- deleted 9y ago[deleted]
- lima 9y agoNo credits given to the PaX Team / Grsecurity :( (PAX_USERCOPY)
- tobiaswk 9y agoHardening an old turd.