6 ms·
Really, a browser is now dependent on a particular Linux kernel? For example RHEL/CentOS 7 which was released just last year with at least a 10 year support ah
by rdtsc 12y ago
Really, a browser is now dependent on a particular Linux kernel?
For example RHEL/CentOS 7 which was released just last year with at least a 10 year support ahead of it is now obsolete according to them because it has a kernel version 3.10...
Not that many people are on desktop versions of those OSes, and those that are will not use Chrome (for example, US govt loves them some Desktop RHEL systems, but Chrome is usually not allowed there anyway), but just highlighting how still seems a bit crazy.
- eeZi 12y agoThe feature might very well be backported to 3.10.
- wtallis 12y agoWhen you commit to a 10-year support cycle, you'd better be prepared to backport quite a few things. Google's being aggressive about taking advantage of a kernel-level security feature that they developed to solve a real problem. This seems like a good thing overall.
- username223 12y ago> When you commit to a 10-year support cycle, you'd better be prepared to backport quite a few things. OTOH, when you make a break-the-world release every six weeks, you can expect lots of breakage when dealing with the rest of the world. From what I can tell, Google pushed a feature they wanted into Linux, then didn't bother to think about backward compatibility. This would be fine if Chrome weren't force-updating software -- people on older kernels could just wait and update when they updated their kernels -- but alas that is not the case.
- pjmlp 12y agoAnd then people wonder why normal users go for Windows and Mac OS X systems for their desktops.
- igravious 12y agoIt'd be nice if they used some of their massive pile of cash to back-port that feature and generate a ton of good will.
- kjksf 12y agoGoogle does a lot of Linux kernel work, a lot of gcc work, a lot of clang work, open-sources monumental amounts of code, pays several hundred students to work on open-source during summer. If that's not enough to "generate a ton of good will" then doing one more minor thing won't change anything. If they start giving out hundred dollar bills, you'll be complaining that it's not two hundred dollar bills.
- igravious 12y agoI'm aware of the work they do. A couple of stupid decisions can cancel out a lot of good will. Not back-porting key pieces of tech and sunsetting products without open-sourcing them is going to counteract the good will they generate. I actually don't dislike Google, and appreciate that they've been a decent open-source player. This is not so minor. If they start handing out hundred dollar bills I would think they'd gone nuts.
- keithpeter 12y ago"Google's being aggressive about taking advantage of a kernel-level security feature that they developed to solve a real problem. This seems like a good thing overall." Yes, it is a good thing for the people who 1) use desktop linux and 2) use a rolling distribution or a distribution that was released within the last year. I suspect that might be a rather small percentage of the Desktop users in the world. It simply means that people who 1) use a desktop Linux and 2) use a stable distribution can't run Chrome (which I imagine solves the security problem in another way). This fraction of a fraction may be larger (corporate desktops, e.g. RHEL, CentOS, Scientific Linux, Debian stable, Ubuntu LTS &c)
- comex 12y agoChrome isn't your average application, though - it pioneered the modern use of tight process sandboxes in general (in client-side applications, anyway), and in particular was the biggest motivating client for (and Kees Cook on Chrome OS Security wrote some of the code for) seccomp-bpf, the ~3-year-old sandboxing mechanism that allows precise control of permitted syscalls and syscall arguments. The incompatibility here is related to a new seccomp feature. I don't know whether it's reasonable to drop support for older kernels, but it's no surprise that Chrome is using the latest and greatest in kernel sandboxing support.
- taeric 12y agoOn the flip side, chrome is also one of the tools used to convince people that web should somehow be equivalent to native. Which, really, just doesn't make any bloody sense. If web pages were content to showing web sites, the vast majority of the motivation for heavy sandboxing, Chrome style, would be irrelevant.
- sebcat 12y agoYou have code running on your computer for rendering the content. Historically, pictures (GDI+ buffer overflow, and others) and .pdf files has been used for exploiting bugs in that code. Sandboxing would have made that a non-issue, or at least less severe of an issue.
- strcat 12y agoIt's still a serious issue even with a sandbox, both because of the endless stream of kernel vulnerabilities and similar issues in userspace processes the sandboxed processes communicate with to get work done. Chromium's use of seccomp-bpf is solely to crack down on kernel vulnerabilities, as it's an additional layer over a sandbox already providing all of the security boundaries they need. It moves things along pretty far, but there are still at least 1-2 holes found every year. It's definitely an improvement over browsers like Firefox where there are at least 3-4 unmitigated remote code execution vulnerabilities fixed every six week cycle...
- 12y ago
- foogoespop 12y agoRHEL/CentOS 6 has been unsupported for quite a while by chrome before this had happened. I assume they'll either drop support altogether or will support RHEL 7 until RHEL 8 is shipped like they did with RHEL 6. They don't care that most people don't jump ship and upgrade RHEL as soon as a new release exists.
- keeperofdakeys 12y agoI don't think the Chrome dev team would want to drop earlier kernels that easily, but this option must help development a lot. From looking, it seems to be something regarding synchronising SECCOMP filters between different threads (SECCOMP is a security sandbox). I imagine this removes quite a bit of code, or fixes some serious corner cases.
- deleted 12y ago[deleted]