Difference between revisions of "Quotes about the September 2019 Avidmaggedon"
| (2 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
"If your computer is on OS X 10.11 or later and you haven’t taken steps to disable SIP, this issue cannot affect you." <ref>https://support.google.com/chrome/thread/15235262?hl=en</ref> | "If your computer is on OS X 10.11 or later and you haven’t taken steps to disable SIP, this issue cannot affect you." <ref>https://support.google.com/chrome/thread/15235262?hl=en</ref> | ||
| + | |||
| + | == Marianna Montague == | ||
| + | |||
| + | "Many Mac users in the editing field try to gleen as much use out of their Mac's and as such, when the OS is updated, a driver or something like TB doesnt work well. They disable SIP, install the "driver(s) needed, and then dont enable SIP back."<ref>http://community.avid.com/forums/p/198021/887033.aspx#887033</ref> | ||
| + | |||
| + | "Another common scanario.... cloning to update many many systems. If the cloned drive has SIP off, the units upgaded end up that way. Had a sight with 85 down and that was why.... chrome keystone update, SIP disables and 10.12.6."<ref>http://community.avid.com/forums/p/198021/887035.aspx#887035</ref> | ||
== apostacy on Hacker News forum == | == apostacy on Hacker News forum == | ||
| Line 20: | Line 26: | ||
== security researcher Sean Wright == | == security researcher Sean Wright == | ||
| − | + | this sort of issue “does not help with the push to encourage people to regularly update their software.” <ref>[https://www.forbes.com/sites/kateoflahertyuk/2019/09/26/google-confirms-buggy-chrome-update-is-breaking-apple-macs/#47dc78a6391c Google Confirms Buggy Chrome Update Is Breaking Apple Macs]</ref> | |
== References == | == References == | ||
<references /> | <references /> | ||
Latest revision as of 17:10, 28 September 2019
Contents
Mr. Macintosh Blog[edit]
"Late Yesterday some #MacAdmins started to report that a few of their systems would not boot properly." [1]
Avid Technology[edit]
"root cause for a reboot issue... is unrelated to Avid" [2]
Google Employee Craig - Chrome Support Manager[edit]
"Chrome update may have shipped with a bug that damages the file system on some macOS machines with System Integrity Protection (SIP) disabled"
"If your computer is on OS X 10.11 or later and you haven’t taken steps to disable SIP, this issue cannot affect you." [3]
Marianna Montague[edit]
"Many Mac users in the editing field try to gleen as much use out of their Mac's and as such, when the OS is updated, a driver or something like TB doesnt work well. They disable SIP, install the "driver(s) needed, and then dont enable SIP back."[4]
"Another common scanario.... cloning to update many many systems. If the cloned drive has SIP off, the units upgaded end up that way. Had a sight with 85 down and that was why.... chrome keystone update, SIP disables and 10.12.6."[5]
apostacy on Hacker News forum[edit]
"My biggest liability now is not malware, but updates! " [6]
security researcher Sean Wright[edit]
this sort of issue “does not help with the push to encourage people to regularly update their software.” [7]
References[edit]
- ↑ https://mrmacintosh.com/google-chrome-keystone-is-modifying-var-symlink-on-non-sip-macs-causing-boot-issues/
- ↑ https://www.avid.com/92419issue
- ↑ https://support.google.com/chrome/thread/15235262?hl=en
- ↑ http://community.avid.com/forums/p/198021/887033.aspx#887033
- ↑ http://community.avid.com/forums/p/198021/887035.aspx#887035
- ↑ https://news.ycombinator.com/item?id=21070515
- ↑ Google Confirms Buggy Chrome Update Is Breaking Apple Macs
