6 ms·
The failures of the Linux core team to properly prioritize security is quite well known. A lot of people have poked the bear by trying to bring this up, also wi
by dmix 7y ago
The failures of the Linux core team to properly prioritize security is quite well known. A lot of people have poked the bear by trying to bring this up, also with specific real examples, and got a tongue lashing from the team and moved on to other things.
I'm amazed the GRSecurity people have managed to do it for so long. Even if merging their stuff mainline legitimately wasn't practical, I've seen plenty of snark and dismissiveness from the Linux team towards them and others. And GRSEC does actively bring in CVEs into their kernel patches all the time and get paid via sponsors to do so.
I'm sure going through old CVEs is a great way to find "zero days" and/or relapses after old patches. Or even just following the work GRSec does there's probably plenty of stuff for a highly motivated company like NSO to exploit.
- telanis 7y agoGRSec is the primary reason the Android devices from BlackBerry have never, to my knowledge, been rooted (despite their many flaws). It's crazy that it's not more accepted.
- dmix 7y agoI personally wouldn't trust a company that openly bragged it built a system to provide local police and Intel agencies with real time access to Blackberry messaging flowing across an entire city in 2010 for G20. In addition to sharing their "master" encryption key for a number of years: https://www.theverge.com/2016/4/14/11434926/blackberry-encryption-master-key-broken-canada-rcmp-surveillance https://www.theverge.com/2016/4/14/11434926/blackberry-encry... Also AFAIK Blackberry only provided a hardened kernel with a single device in 2015 called Priv. I haven't heard anything from them since... maybe someone could correct me here.
- westmeal 7y agoThe new Android devices also have hardened kernels but it doesn't really matter phones are insecure as fuck in other ways.
- justinjlynn 7y agoIndeed. Who the hell thought it was a great idea for the modem baseband device to have unlimited direct memory access to the host processor memory space? I mean, especially when the baseband firmware can usually be remotely updated by the network with zero user interaction?!
- posix_me_less 7y ago> have unlimited direct memory access to the host processor memory space Can you give some reference for that claim?
- jsjohnst 7y agohttps://www.usenix.org/system/files/conference/woot12/woot12-final24.pdf https://www.usenix.org/system/files/conference/woot12/woot12... If you want more, literally google “baseband attack host processor memory” or “baseband exploits DMA” or “baseband exploits memory”.
- diroussel 7y agoIs this all Android? Or just Blackberry?
- pnako 7y agoIf you submitted a huge patch to Linux that would really improve support for real-time audio, but break many other things like IO throughput, etc. but your argument for accepting it anyway was "yes, but it's for real-time audio support, so it's really important and more important than what everyone else is working on", you'd be laughed out of the mailing list. The fact you use the word "prioritize security" is indeed telling. Security is just one aspect of a system. There is no particular reason for Linux to prioritize it above everything else, no matter what twitter infosec drama queens believe. Obviously the fact that infosec people are quite often insufferable does not help their case.
- kuzimoto 7y agoWhen you're developing such a crucial part of an operating system, wouldn't you want to put security pretty high at the top of the priorities list? If I were an average consumer, I would care much more about my device being secure, than having real time audio.
- pnako 7y ago>If I were an average consumer If you were, you would behave like one, i.e. not care that much (if at all) about security. What you are saying is "I do care about my device being secure".
- kuzimoto 7y agoYes, I suppose that's true. I should have worded it differently. Perhaps, the average person would be more upset/notice if they were negatively impacted as the result of a security issue, than if some feature, e.g. real time audio were missing, which I'm sure no one would even notice.
- girvo 7y agoYou’d think no one would notice real time audio being missing on android devices, but that discounts the huge amount of music creation thats done on mobile platforms these days. It’s a way bigger market than you’d think!
- fooker 7y agoThere is no 'Linux core team'
- panpanna 7y agoThere is one, but they have nothing to do with this. This falls pretty much on Google and people in charge of the backports
- pjmlp 7y agoSure there is, the ones with commit rights to validate pull requests.
- fooker 7y agoThat is too large to be considered 'core' and too unstructured to be considered a 'team'. Hence these issues, arguably.
- lucb1e 7y ago> failures of the Linux core team But isn't the issue that Android didn't merge it? Linux patched it.
- dexen 7y ago>The failures of the Linux core team to properly prioritize security Why even post this, when it has nothing to do the with the case GP & OP described? It's misleading at best. The failure here is in the way Google has set its Android development process. They keep a separate "stable" kernel, and manually select certain patches to backport to. In process they skip all kinds of patches - performance, features, and yes, security ones. Given that only selected patches are backported, the process is best described as insecure by default. It was Google's decision to favor stable API over security here. This is compounded by the fact other Android phone vendors are pretty slow at releasing OS upgrade - and tend to stop releasing them altogether shortly after the phone's no longer manufactured. The mainline kernel, as released by the Linux core team is up to date with security. Hold to account people that decided to skip patches as a matter of course, resulting in the insecure by default process.
- viraptor 7y ago> The failure here is in the way Google has set its Android development process. I think it's still the won't layer. Google may be able to put some pressure to change things, but it's describe the issue as "the failure is in the way SOC manufacturers have set their kernel porting process". You often get chips which work with one version and a dump of specific drivers. Beyond pressuring the company to upstream their changes, or writing clean room versions, I don't see many solutions.
- typical182 7y ago> The mainline kernel, as released by the Linux core team is up to date with security. Hold to account people that decided to skip patches as a matter of course To me, the particulars of this exact case are not as interesting as the fact that the entire Linux patching and backporting of security issues seems _very_ fragile, with things frequently getting "lost" for mundane reasons, and a key part of the "why" it is so fragile is due to many of the core Linux development processes. This particular CVE is apparently one small example that happened to catch some headlines out of _thousands_ of similar problems. That talk linked above by Dmitry Vyukov is worthwhile for getting a sense of the magnitude of the problem.
- sukahiroaki 7y ago