8 ms·
The Truth about Linux 4.6
- zxcvcxz 11y agoAre any big companies using the grsecurity patches?
- josh64 11y agoI think BlackBerry use them on their Android kernels.
- hga 11y agoDocker is using Alpine Linux which normally uses grsecurity.
- cm3 11y agoDoes Docker boot a kernel?
- ysleepy 11y agoDocker is just a beefed up wrapper around groups of processes on linux.
- contingencies 11y agoDocker just resolved a critical compatibility issue it had with most reasonably useful configurations of grsec... see https://github.com/docker/docker/issues/20303 https://github.com/docker/docker/issues/20303 which I opened, and https://github.com/docker/docker/pull/22506 https://github.com/docker/docker/pull/22506 which solved it.
- cyphar 11y agoI'm not sure why they went with pivot_root -- there's already code to deal with handling symlinks and all of their paths properly within Docker containers from the host (which I helped write and merged something like 2 years ago). I would've thought the obvious way of doing it would be to modify pkg/archive ...
- viraptor 11y agoThat doesn't give you any improvement in the container by default. Only the host's kernel matters in case of grsec.
- cyphar 11y agoDocker doesn't boot a kernel. It uses host kernel features. People who use alpine as a base for Docker images are just using the root filesystem from an alpine install.
- jordigh 11y agoThat's a lot of trash-talking from someone who knows how to dish it but not take it: http://www.theregister.co.uk/2016/04/27/linux_security_bug_report_row/ http://www.theregister.co.uk/2016/04/27/linux_security_bug_r... I don't know who's right or wrong, but I wish Linux people (both sides) behaved more civilly. Linus breeds an atmosphere where personal attacks and insults are encouraged in the name of supposedly better code.
- striking 11y agowrt link: Marcan's only crime was being a little cheeky. It didn't warrant the total meltdown/blockfest spender had. And on topic: Why can't the grsecurity patches just be merged into the kernel?
- GunboatDiplomat 11y agoMy understanding is that it breaks things.
- JoshTriplett 11y agoQuite a lot of things. The problem with grsecurity's claim that Linux doesn't care about security is that grsecurity doesn't appear to care about anything but security. They include changes with significant performance impact, changes that break existing userspace programs, and changes that significantly impact the maintainability of the kernel. Security that people can't or won't use doesn't actually make people more secure; usability, performance, compatibility, and other such concerns are all part of building a secure system. grsecurity has done a huge amount of innovation in kernel security, and they deserve quite a bit of credit for that. But grsecurity made a very public and vocal decision to no longer attempt to get any of that work into the upstream kernel, because they don't enjoy having to deal with the process involved in collaborative development. Instead, they went off and built a company around their out-of-tree work, and try to advocate that people use it. Meanwhile, some of the ideas that grsecurity pioneered (and a lot of other security innovations from other sources too) have started to make their way into the kernel, championed by people who are willing to do the work and participate in a collaborative development process. And the repeated response from grsecurity involves public whining, bashing of people doing the work they refuse to do, and, of course, advertisement. Whining that Linux doesn't have the security technology that they do seems rather hollow coming from people who very vocally gave up on doing the work to actually make Linux better. Out-of-tree, out-of-sight, out-of-mind.
- Animats 11y agoThe two big security falsehoods: - Recognizing known attacks (as with virus signatures) is effective. - Patch and release is effective. That sort of worked back in the script kiddie era, when the attacker was some kid in their parents' basement. They stopped working when the attacker became organized crime, usually from Russia and China. They became hopeless when the attacker became nation-states.
- contingencies 11y agothe attacker became organized crime, usually from Russia and China {{citation-needed}} You don't think people bounce through boxes in jurisdictions with cultural/linguistic/political LE collaboration challenges on purpose? I'd wager a fair amount of so-called Chinese traffic is in fact foreign in origin.
- coredog64 11y agoIf the PLA or Russian mafia really wants something in your network, they will threaten to cut off your spouse's/kid's thumbs. Grsec isn't going to protect against that.
- zanny 11y agoIt is eternally frustrating how valuable kernel features like grsec, the bfq and bfs schedulers (for disk and cpu respectively), and many more hugely useful but not commercially backed (or at least proposed) projects wallow in side trees of Linux mainline. It is just baffling how the grsec patches are ~13? years old now and yet remain out of tree rather than, say, default-off on kconfig, which even then makes no sense - users of the kernel should be getting maximally secure and conservative software first, and then turning off checks to increase performance, not the other way around - having a wild and exploitable kernel you need to use out of tree patches to get under reasonable control.
- CrLf 11y agoIf there's something that defines the Linux kernel development process is that large/wide changes are never accepted in bulk. Changes must be broken up into independent pieces that make sense by themselves and can be well understood by the people doing the merges. For example, if you want to introduce a new filesystem that requires VFS features not yet present, you submit those features first and make a case for their usefulness beyond your own use case. Then you submit your new filesystem adapted to use those features as they where (then already) merged. Failing to go through this process results in failure to be accepted for inclusion in mainline. Sure, this makes some useful stuff linger by the wayside (usually due to ego clashes), but it's the only way to maintain any sanity in a project as large and active as the Linux kernel and that's a good thing in the long run.
- DominikD 11y agoAFAIK they never tried submitting in bulk so I'm not sure why this (sensible, I think) process is used as an argument against them. I don't know if they tried to post piece by piece (and when/if they gave up). But there's a pretty well documented anti-grsecurity sentiment on the lists dating waaaay back. So if I were them I wouldn't be necessarily convinced that I should invest my time in slicing to begin with. ;)
- cyberpunk 11y agoYou don't evolve proper security though a million tiny commits. You design it. This is why containers on Linux will probably never have the security that Solaris or the BSDs have, and this attitude is why. It will never get better until that is rethought, if you're right..
- CrLf 11y agoWhenever I read (or hear) about how grsecurity improves things I wonder why it isn't included in mainline, or why isn't it in the process of being included in mainline. This is, of course, a rethorical question that usually gets an answer that vaguely reminds me of the Reiser4 threads of yesteryear.
- DominikD 11y agoIt's the same reason other interesting things don't get mainlined from time to time: personalities and opinions. Linus is a loudmouth and he has every right to be like that. It's his playground after all. But this leads to blind spots and dogmatism in areas that ultimately hurt the project. In case of grsecurity Linus tends to disagree with their philosophy of what leads to more secure system and what doesn't. And if Linus thinks you're wrong, then you're wrong, period. So grsecurity crowd would have to bow and compromise (which collides with their philosophy) on what stuff gets integrated, how, etc. What's good enough according to Torvalds is not good enough according to them. But let's say they kneel. They'd have to not only cut their baby in pieces and massage it over and over again, discussing every detail of design and implementation on the list for Linus to mercifully accept it, they'd invest time pleasing him instead of doing what they care about: improving security. So it's a lose-lose for them. And mainline doesn't seem to care about security (contrary to popular belief I guess). So yeah, there you have it.
- CrLf 11y agoYou overestimate Linus' role in the process. The process is hierarchical and by the time patches reach Linus they're already bulk by the very definition of it. What leads to better security? Having an out-of-tree patch that few people use, or include parts of it in mainline thus benefiting everyone? Eventually most, if not all, of their changes would reach mainline. Also, is it good for security to accept bulk patches touching all kinds of sensitive parts of the kernel? I'd say that the existing process is better for security in the long run. This process isn't about bowing to anyone, and thinking about patches as someone's baby doesn't help either. This happens every day with patches from companies with deep pockets and big influence and they end up going along with the program to get their stuff accepted. The result is invariably better than the original bulk patch.
- cm3 11y agoPersonalities and history of GRsecurity not taken seriously in the past led to a grumpy Spender who now has a hard time collaborating with kernel.org when they are actually funding work in the space. At least that's my impression from following this for years. HardenedBSD tried to upstream their ASLR patch and the developer didn't manage to address the patch review comments (if you check the Phabricator ticket) and another FreeBSD kernel dev (Belousuv) contributed his ASLR patch upstream in FreeBSD-11. Before this happened, HardendedBSD decided to not try upstreaming stuff, but they still, like GRsecurity, have very useful security enhancements and it only hurts FreeBSD users having to decide between FreeBSD and HardednedBSD (or a HardendedBSD variant of FreeNSD or OPNSense). I know firsthand how strong personalities can be very hard to work with if you cannot get your technical argument across, so I don't really blame Spender, but it's a disservice to all users. It's not like music where you can listen to both bands. A computer starts up with one kernel at a time. It might actually help to get the PaX/GRsecurity team and core kernel lieutenants in a room for a couple hours to talk it out and realize they're not disagreeing.
- kev009 11y agoHardenedBSD is some young people that have very little experience with C and computer architecture picking bones against some people in the FreeBSD community who have that experience in spades and becoming angsty and upset that they are unable to meet requisites for merge. Altering the VM doesn't happen quickly, especially when you have no track record of working on that subsystem. Comparing HBSD to grsecurity is insulting to grsecurity, there is no similarity.
- cm3 11y agoThat wasn't my impression, but I'm not qualified to judge the diffs on the code level, so I'll note that their changes may possibly be of lower quality than they are advertised.
- cm3 11y agoRelated submissions: https://news.ycombinator.com/item?id=11637933 https://news.ycombinator.com/item?id=11637933 https://news.ycombinator.com/item?id=11636710 https://news.ycombinator.com/item?id=11636710
- dfc 11y agoRelated submissions = Stories you submitted that have no comments and did not receive the karma boost you were hoping for.
- odonnellryan 11y agoDoes that make them not related?
- odonnellryan 11y agoDoes that make them not related?
- cm3 11y agoHN's dupe finder isn't perfect and it has no sections, so rather than having new submissions I thought it'd be better to reuse existing entries. That said, I can see how my comment may appear as it did to you, but that wasn't my intention. Maybe I should have deep-linked.
- dang 11y agoOn HN the convention is to link to previous submissions if there's interesting discussion there, but not otherwise. We allow reposts as a way of giving interesting stories multiple chances at attention—otherwise most interesting stories would be sunk by randomness, making this place less interesting. (And thanks for responding to a provocative comment with exemplary civility!)
- dang 11y agoPlease don't be personally rude.
- massysett 11y agoHow does grsecurity compare to SELinux and AppArmor? Aren't SELinux and AppArmor both in the kernel?
- viraptor 11y agoGrsec consists of a few systems. One of them is RBAC, which is an access control part for userspace applications. It works similar to selinux/apparmor, but it's not based on LSM interface (as far as I know, but feel free to correct me). Compared to SELinux, RBAC misses some very specific features, like dbus calls filtering for example, but otherwise those 3 systems are fairly comparable. RBAC uses AppArmor approach of filtering based on paths rather than inodes/attributes. But grsec as a whole is much larger. It prevents way more attacks at kernel and userspace level than LSM implementations can see. https://grsecurity.net/compare.php https://grsecurity.net/compare.php should give you a general idea. Also, there's nothing preventing you from using selinux, apparmor, or something else with grsec kernel - they can still run together.
- leni536 11y agoI lot of people here wonder why grsec isn't merged into mainline. I just read this recently related to grsec: https://twitter.com/marcan42/status/724745886794833920 https://twitter.com/marcan42/status/724745886794833920 This is really poor communication from both sides.
- Karunamon 11y agoSounds like someone WTFed at garbage code manifesting in an insane failure case and the author threw a temper tantrum.
- based2 11y agohttps://wiki.debian.org/grsecurity https://wiki.debian.org/grsecurity