13 ms·
No, it wasn’t a virus; it was Chrome that stopped Macs from booting
- java-man 7y agoThis basically tells about the state of computer security in general. There is no isolation of OS from applications, or between the applications. This is by design, dated back to early unix times. We will continue to see these issues until there is a brand new OS which isolates subsystems by design. That is, each application/process gets not only own address space, but own file system, own settings store, with the OS carefully managing cross-boundary accesses.
- mixedCase 7y agoFrom TFA: > When SIP was enabled—as it is by default—SIP worked as designed and prevented the change. When the protection was disabled, however, the file system was modified in a way that prevented Macs from rebooting.
- java-man 7y agowhat is the rationale for disabling SIP? not only there should be no way to disable this protection, it should be a deliberate design goal to prevent any process or application from accessing protected areas.
- saagarjha 7y ago> what is the reationale for disabling SIP? Loading unsigned drivers for eGPUs. > not only there should be no way to disable this protection, it should be a deliberate design goal to prevent any process or application from accessing protected areas. I think you're looking for iOS.
- java-man 7y agoiOS: https://www.cvedetails.com/product/15556/Apple-Iphone-Os.html?vendor_id=49 https://www.cvedetails.com/product/15556/Apple-Iphone-Os.htm... loading dev drivers should be done differently, and limited to dev, not production. the fact that one needs to disable security feature in production indicates a bad design. i.e. the user may explicitly allow loading of particular objects (using hashes).
- saagarjha 7y agoI don't understand why you're linking to a CVE list.
- httpsterio 7y agoSome gpus need SIP on off because the drivers won't run else. I generally also have to disable it because I run some apps and modify some underlying behaviours in macOS that I find undesirable. I don't think it should be any worse than running stuff as sudo on Unix, where you can easily break the whole OS if you, as the user, don't know what you're doing. Chrome had a bug and even if it wouldn't have broken the system had SIP been enabled, it's still a serious bug on chrome's side.
- protomyth 7y agoPerhaps if Apple would let us self-sign drivers on our computers, we wouldn't need to disable SIP. Security that does not allow the actual use of the computer gets disabled.
- EricE 7y agoExactly. Apple still hasn't come to terms with balancing security with functionality.
- dreamcompiler 7y agoYes, 100% this. SIP is badly designed because it's a global hammer like root. As such, it prevents power users from doing quite legitimate things with their computers and so we have to turn it off. SIP should work like sudo, not like meta-root.
- GeekyBear 7y agoYou can whitelist a kext. https://eclecticlight.co/2019/06/01/how-to-bypass-mojave-10-14-5s-new-kext-security/amp/ https://eclecticlight.co/2019/06/01/how-to-bypass-mojave-10-...
- saagarjha 7y agoI'm fairly sure this only applies to KEXTs that are signed but not notarized.
- damnyou 7y agoSometimes you want to do things that the OS maker does not want you to do, like run dtrace on system binaries. If you had no recourse to bypass the OS maker, the world would be a much worse place.
- bjtitus 7y agoSo iOS?
- java-man 7y agoright. https://www.cvedetails.com/product/15556/Apple-Iphone-Os.html?vendor_id=49 https://www.cvedetails.com/product/15556/Apple-Iphone-Os.htm...
- bjtitus 7y agoNo one said isolation solves all security vulnerabilities. I'm not sure what else you'd expect from one of the most widely used software platforms ever made.
- curt15 7y agoOr Flatpak? Firefox is making progress on that front: https://bugzilla.mozilla.org/show_bug.cgi?id=1441922 https://bugzilla.mozilla.org/show_bug.cgi?id=1441922
- overgard 7y agoSo.. containers.
- java-man 7y agohttps://www.cvedetails.com/vulnerability-list/vendor_id-13534/Docker.html https://www.cvedetails.com/vulnerability-list/vendor_id-1353... Total number of vulnerabilities : 26
- kps 7y agoThe problem with that — for users — is that it is likely to lead to the phone-style data roach motel, where applications control users' content and hold it hostage from them.
- coryrc 7y agoProgrammers developed containers and kubernetes to cover this space, but we haven't created a consumer OS with programs each in their own container.
- wozer 7y agoAndroid ist a bit like this, isn't it?
- techntoke 7y agoNot really. Containers run natively and use the built in kernel features to sandbox. Android uses the Java VM.
- java-man 7y agoAndroid aside, the use of JVM might offer a better alternative (because of bytecode validation). One way to achieve security is to enforce what an application/process can do is via specialized interfaces. For example, java.io.File will only see a virtual application filesystem, and one would need to grant special permissions (via a different interface) for file access outside of the app sandbox. These permissions should be controlled (and audited) by the user. Possibly at more levels than currently (blocked/allowed always/while running).
- monocasa 7y agoThat was tried by the sun JVM, and worked until they tacked on reflection. Then there was just too many ways to break the sandbox when the sandbox is implemented just like your code is and you've got a mechanism for doing brain surgery on the process. Every time they'd fix a applet sandbox escape two more exploits would pop up.
- java-man 7y agoSecurity must be the primary design goal, at least right now. I don't think the way Sun implemented permissions in java offers enough protection.
- ga-vu 7y agoPrevious discussion: https://news.ycombinator.com/item?id=21064663 https://news.ycombinator.com/item?id=21064663 https://news.ycombinator.com/item?id=21073819 https://news.ycombinator.com/item?id=21073819
- ColinWright 7y agoThanks, I went looking for a previous submission, but couldn't find one. I figured if I posted it myself someone would provide the pointer. I'll leave this here to capture other submissions of this source. Cheers. EDIT: Also, interesting to read the discussions there.
- ga-vu 7y agoBetter if you'd stop submitting ArsTechnica stuff. All that site does is take other outlets' articles and run them as their own. I'm surprised nobody has sued already, especially since they have a subscription service asking for money for stuff that other people research and publish first.
- protomyth 7y agoI still don't understand why Google needs to have something more than the basic update functionality that other Mac Apps have via libraries like Sparkle?
- kevingadd 7y agoGoogle runs a system-level update service on Windows too. The crash handler for it is also running all the time, at least on my machine (and is running with root-equivalent permissions). If you disable it, the next time you launch Chrome they just turn it back on. It's bizarre. Few vendors do this.
- mcny 7y ago> Google runs a system-level update service on Windows too. The crash handler for it is also running all the time, at least on my machine (and is running with root-equivalent permissions). If you disable it, the next time you launch Chrome they just turn it back on. > It's bizarre. Few vendors do this. Please correct me if I am wrong but Adobe Reader has something like this on Windows, right? And so does iTunes?
- Silhouette 7y agoEven Apple and Adobe don't actively turn their update services back on when you run their applications if you have explicitly disabled them, though, at least not in any version of any of their software that I've come across. In contrast, it appears that Google installs whatever updates it wants on your system and does turn the related services back on again if you turn them off. It really shouldn't be possible for software to leave that sort of access open without the user's/administrator's explicit consent, but unfortunately the worst offender on this issue is now Microsoft with Windows 10, so I don't hold out much hope that anything will be done about it on Windows platforms any time soon. Sadly, this just seems to be the price of admission to the modern software world. You have what is effectively a permanent rootkit installed if you want to use the software at all, and even though that is self-evidently incompatible with a robust security and privacy model, when big enough players do it, people just accept it because they don't see that they have any choice.
- EricE 7y agoremoved /var? How the hell does that get past QC? Also heartily agree with other comments about Google's update processes in general. Trust is still a house of cards in computing :(
- TheCoreh 7y agoMy understanding is that /var was only removed on systems without SIP enabled, the recommended (and default) setting. This only affected users who went out of their way to disable this security feature. Presumably Google QA had this enabled on all their machines.
- tannhaeuser 7y agoThat's hardly an excuse, is it? The question is whether, after this incident, you're still comfortable with using any Google app.
- cloudwalking 7y agoHow many Chrome updates have you gotten that did not break your computer? Was your computer broken by this? My understanding is the rollout was stopped fairly quickly.
- zepto 7y agoHow many other equally dangerous and irresponsible mechanisms are Google using?
- deleted 7y ago[deleted]
- hinkley 7y agoHow many times did Ann Rule interact with Ted Bundy and he didn't murder her once? I mean, he can't be all that murdery, right? We're talking about nuking a filesystem, not glitching out randomnly. That it hasn't nuked the filesystem before is not extenuating circumstances. It doesn't speak to character either.
- jacquesm 7y agoApplication level software should 'stay in its lane'. Chrome and the Chrome updater shouldn't even have this level of capability.
- minikites 7y agoWhich is why SIP exists.
- favorited 7y agoThankfully, with SIP, they don't.
- MuffinFlavored 7y agoedit: not https://en.wikipedia.org/wiki/Session_Initiation_Protocol https://en.wikipedia.org/wiki/Session_Initiation_Protocol, https://en.wikipedia.org/wiki/System_Integrity_Protection https://en.wikipedia.org/wiki/System_Integrity_Protection for anybody else
- Doctor_Fegg 7y agoNope, https://en.wikipedia.org/wiki/System_Integrity_Protection https://en.wikipedia.org/wiki/System_Integrity_Protection .
- mxuribe 7y ago> varsectomy... That's awesome! Well, the name is awesome, not the digital "surgical" procedure, of course. ;-)
- tzs 7y agoOK, so unlinking /var is a varectomy. That fits. I suppose if instead you just deleted random files from /var, that would be a varotomy? I can't think of anything, offhand, that would be a varostomy. For those unclear on the difference between -ectomy, -otomy, and -ostomy, see [1]. https://www.straightdope.com/columns/read/607/in-medicine-whats-the-difference-between-an-ectomy-an-ostomy-and-an-otomy/ https://www.straightdope.com/columns/read/607/in-medicine-wh...
- iamdumb 7y agoDid Chromium users on MacOS have this issue as well? If not, what is Chrome doing differently than Chromium?
- jeroenhd 7y agoAs far as I know, Chromium itself doesn't support automated updating. There are third party updating tools for most platforms, but the automatic updater from Google is not used for Chromium.
- holy_city 7y agoDisclaimer: this affected me tangentially which is why I've been trying to figure out what exactly happened and where it came from. The issue was not Chrome in and of itself, but Google Keystone, which is the update daemon for Chrome. I don't think Keystone is open source so you can't grep for 'unlink("/var")' to figure out what was going on.
- midnitewarrior 7y agoThe fact this was accidental is far worse than a virus.
- wokkel 7y agoEverybody seems to be reading over the fact that the logged in user must be able to write to /. Is this common for macOS users? If so there is a significant pebkac factor as well.
- soneil 7y agoIt's not dependant on the logged-in user, keystone is a background agent (daemon) that handles Google's updates. The expected scenario is that the browser is installed by an administrator (a sudoer), and the keystone agent is installed the same. The background agent runs as an elevated process specifically to remove the dependency on the logged-in user .. but with the side-effect that you're now trusting Google not to remove /var. Because, yaknow, we generally assume Google aren't that clueless. Then we have a layer below that, "System Integrity Protection" (further enhanced by read-only-root in 10.15) which stops processes removing such vital parts of the OS, even if they are root. Which is where the Avid red herring came from. If you need to install unsigned kernel extensions, you need to disable SIP. And it turns out third-party video drivers are popular with the video editing crowd - so they had a much higher prevalence of users running without SIP.
- fortran77 7y agoThis is why I run Firefox. Because it's written in Rust, these things simply can't happen.
- jasonmp85 7y agoYou’re trolling, right?
- beatgammit 7y agoI sure hope so because everything about that statement is wrong.
- dreamcompiler 7y agoIncluding the implicit assumption that this was somehow a Chrome problem. It wasn't. It was a Keystone problem, and Keystone is a separate program that updates Chrome and Earth and other Google products. Still very much Google's fault, but Chrome didn't cause the issue.
- fortran77 7y agoDoesn't Mozilla write their installers and related programs in Rust, too?
- hnghost 7y agoI'll step up and say it. Google in 2019 is a bloated and incompetent company consumed by internal politics that has no vision. Chrome has been nothing but a ploy for google to ruin the web from the get go.
- dehrmann 7y ago> no vision Missing the boat on cloud computing while they were flailing away at social is pretty strong evidence of that > ruin the web The web was pretty bad pre-Chrome. Browsers were much slower and much less compatible. Things started to get worse once Chrome market share got to a third, or so, and Google started driving the direction of the web.
- logogo 7y ago[url=http://www.philadelphiaoutcallescorts.com]Philadelphia http://www.philadelphiaoutcallescorts.com]Philadelphia asian escorts[/url]
- hnghost 7y agoIt's not that Chrome itself is a problem but rather the way that Google releases updates for Chrome which damages the ecosystem. Build a good browser that helps users load elements faster and enjoy the web more? Always good! Changing this same browser to make your sites load faster while not announcing these changes so your competitors scramble while meanwhile you go "what, me worry?" Just pathetic really. It's not like they were trying to push us past some inefficiencies, just taking us to ones they owned.
- SN76477 7y agoRemember when Chrome was flaunted as the fastest browser? Now it's just bloated.
- tsm 7y agoI do, but I also switched back to Firefox recently (after using Chrome for ten years) and it's slower. What _is_ the fastest feature-complete browser in 2019?
- TazeTSchnitzel 7y agoThis shows why System Integrity Protection is a great feature for most users. Even an application running as root can't easily hose the system.
- holy_city 7y agoMy guess with what happened is that they were downloading to /var somewhere and messed up a variable name when they called unlink() to remove their temporary data, which when running as root would delete the symlink of /var to /private/var. It wouldn't be caught if they weren't testing without SIP enabled, on older macOS versions, and rebooting as a part of the test suite. E.g. I'd put a dollar on this being a variable naming bug, where they called unlink(temp_dir) instead of unlink(temp_dir_where_we_put_stuff), with the former being "/var".
- kjhughes 7y agoThe Mr Macintosh blog (which the Arstechnica piece cites) has more technical details: https://mrmacintosh.com/google-chrome-keystone-is-modifying-var-symlink-on-non-sip-macs-causing-boot-issues/ https://mrmacintosh.com/google-chrome-keystone-is-modifying-...
- vgetr 7y agoRemember when browsers were for, you know, browsing?
- jomoio 7y agoThis reminded me of the time I mistakenly deleted /var/tmp/ instead of just deleting the contents of /var/tmp/. The router was not pleased.
- scandox 7y agoI once deleted /usr ... Instead of /some/sub/dir/usr It was interesting to see things like fonts disappearing randomly from web pages etc as my computer progressively went mad.
- sam_goody 7y ago> No, it wasn't a virus. Chrome is spyware that can be used to browse the web (while advancing the agenda of the ad company that built it). Since spyware is loosely classified as a virus, I would beg to differ with the headline. By the way, aside from all the "regular tracking" it does, did you know that the Chrome updater spawns programs with random names that write other programs with random names. Sounds like a virus? And just check out what it is doing to get you past a captcha... you can't. It is on a OS level, not a browser level, and everything about what it is doing is VERY obfuscated. Very virusy IMO?
- shawkinaw 7y agoOff topic, but > system integrity prevention would be a pretty funny OS "feature".
- detail-oriented 7y agoI don't use chrome any longer, firefox for the win.
- dreamcompiler 7y agoIt wasn't Chrome either. It was Keystone, a separate program that updates Chrome and other Google programs. Most users have never heard of Keystone (and Google likes it that way), but Keystone is running on your computer if you've ever used Chrome or Earth or another Google program. A bug in Keystone caused this problem. Keystone is very hard to kill and if you succeed in killing it it has a nasty tendency to come back. Keystone is malware written by Google and it needs to die.
- monocasa 7y agoTo be fair, updater software for security conscious apps have good reasons to be hard to kill. Even outside of an attack scenario, you want to give as much chance as possible for your apps to still update even if you shipped a crashing bug or something.
- dreamcompiler 7y agoUnkillable software also has a very high bar for quality. That means among other things that it needs to be a good citizen on my computer and have pristine quality control. Keystone is neither and never has been. With great power comes great responsibility, and Google blew it.
- dmix 7y agoPlus it's one thing to be difficult for malware to kill and another for it to be impossible to disable for privacy or maintenance reasons. It's a tradeoff that favours Google and imposed by the unilaterally. I could think of a few ways this could be addressed without forcing it. Such as detection from the browser app when it's not available.
- monocasa 7y agoI mean, I'm going to judge them when I stop writing bugs. Until then, a zealous updater seems preferable to leaving browsers around with CVEs, even with this massive fuck up on their plate.
- fortran77 7y agoIt's a Good Idea not to install any additional software, whether it's a browser that's not the one bundled with the OS, Spotify, Slack, etc, on a machine that's being used for production builds, editing. We don't put anything that's not absolutely necessary on our build machines, for example.
- KenanSulayman 7y agoAn interesting side effect of the Keystone daemon is that Google is receiving pings from all users running the software. I'm very sure that this enables Google to proactively track users without only relying on persistent cookies. Add Google DNS on top and you get a seamless, massive scale RUM solution.