Razer Leviathan V2 gaming soundbar review
Guru3D NVMe Thermal Test - the heatsink vs. performance
EnGenius ECW220S 2x2 Cloud Access Point review
Alphacool Eisbaer Aurora HPE 360 LCS cooler review
Noctua NH-D12L CPU Cooler Review
Silicon Power XPOWER XS70 1TB NVMe SSD Review
Hyte Y60 chassis review
ASUS ROG Thor 1000W Platinum II (1000W PSU) review
ASUS ROG Rapture GT-AXE11000 WIFI6E router review
Backforce One Plus Gaming Chair review
Google Chrome adds Protection against Meltdown and Spectre
Earlier last week we've already reported that Chrome would get HDR support, e.g. the ability to play for playing HDR content. However, it also adds protection for Windows and Mac OS, the so-called SharedArrayBuffer is disabled.
Another handy new feature is the ability to 'mute' the sound per domain. So if you get a website that by default plays tunes, or their ads do, with this feature it's muted by default once you have it enabled. By right-clicking the website tab, you can enable it:
As mentioned, this latest version of Chrome also protects Mac and Windows users against the Meltdown and Spectre vulnerabilities. Google is disabling the SharedArrayBuffer feature to mitigate against web-based attacks. The update will apply itself, or alternatively, you can manually update by going to help and then about.
Google Chrome Adds Support For HDR Video Playback - 01/24/2018 06:00 PM
Google send word about an update with the Chrome browser over the last year and offered a peek at some features that will arrive later this year. To start, Chrome now supports play/pause, rewind, and ...
Microsoft Announces Windows 10 S To Take On Google Chromebook - 05/02/2017 04:43 PM
Microsoft has launched Windows 10 S. Windows 10 S is a version of the OS targeted at students of all ages that promises higher performance, better battery life, and tighter security....
AMD Radeon Technology Will Be Available on Google Cloud Platform in 2017 - 11/16/2016 10:27 AM
AMD announced that Radeon GPU technology will be available to Google Cloud Platform users worldwide. Starting in 2017, Google will use AMD's fastest available single-precision dual GPU compute accele...
Photos New Google Chromecast are online - 09/18/2015 08:07 AM
Photo's of the upcoming and thus new generation model Google Chromecast surfaced on the wen yesterday. The photos are quite horrible but do show some intersiting stuff for this audio & video str...
Google Chromebook Pixel notebook starts at $999 - 03/12/2015 08:32 AM
Google has unveiled its second-generation Chromebook Pixel - and it's a good deal cheaper than its predecessor. The new Pixel starts at $999, and it has some pretty decent specs to match its premium ...
Robbo9999
Senior Member
Posts: 1613
Joined: 2012-10-07
Senior Member
Posts: 1613
Joined: 2012-10-07
#5514624 Posted on: 01/26/2018 09:48 PM
Ha, yep, I just used it, great idea!
To other folks and anyone out there, does the included Meltdown & Spectre fix in this latest version of Chrome do the same thing as "Strict Site Isolation" in this chrome flag? chrome://flags/#enable-site-per-process
Or is it better to leave "Strict Site Isolation" enabled in the new version of Chrome? (Enabling "Strict Site Isolation" was advised to protect against Meltdown & Spectre on the previous version of Chrome, but don't know if it's necessary in this new version). At the moment I have "Strict Site Isolation" enabled on the latest version of Chome (Chrome 64), and it seems fine - I have a feeling that this flag provides protection above & beyond the Meltdown/Spectre fix shipped with Chrome version 64.
Love the mute tab idea.
Ha, yep, I just used it, great idea!
To other folks and anyone out there, does the included Meltdown & Spectre fix in this latest version of Chrome do the same thing as "Strict Site Isolation" in this chrome flag? chrome://flags/#enable-site-per-process
Or is it better to leave "Strict Site Isolation" enabled in the new version of Chrome? (Enabling "Strict Site Isolation" was advised to protect against Meltdown & Spectre on the previous version of Chrome, but don't know if it's necessary in this new version). At the moment I have "Strict Site Isolation" enabled on the latest version of Chome (Chrome 64), and it seems fine - I have a feeling that this flag provides protection above & beyond the Meltdown/Spectre fix shipped with Chrome version 64.
BlackZero
Senior Member
Posts: 8878
Joined: 2007-06-17
Senior Member
Posts: 8878
Joined: 2007-06-17
#5514687 Posted on: 01/27/2018 02:53 AM
I was wondering the same thing, as the message in the setting reads the feature is highly experimental and could in fact compromise security (?), and I've recently had trouble logging into some sites.
I've decided to disable it for now, as the new update is obviously already meant to take care of the issue.
I was wondering the same thing, as the message in the setting reads the feature is highly experimental and could in fact compromise security (?), and I've recently had trouble logging into some sites.
I've decided to disable it for now, as the new update is obviously already meant to take care of the issue.
RealNC
Senior Member
Posts: 3671
Joined: 2011-11-24
Senior Member
Posts: 3671
Joined: 2011-11-24
#5514700 Posted on: 01/27/2018 04:58 AM
Do you happen to know why they excluded Linux from this?
this latest version of Chrome also protects Mac and Windows users against the Meltdown and Spectre vulnerabilities.
Do you happen to know why they excluded Linux from this?
Robbo9999
Senior Member
Posts: 1613
Joined: 2012-10-07
Senior Member
Posts: 1613
Joined: 2012-10-07
#5514706 Posted on: 01/27/2018 07:39 AM
I was wondering the same thing, as the message in the setting reads the feature is highly experimental and could in fact compromise security (?), and I've recently had trouble logging into some sites.
I've decided to disable it for now, as the new update is obviously already meant to take care of the issue.
I did some research just now and found the official in depth description of Strict Site Isolation from the people who developed the software: http://www.chromium.org/Home/chromium-security/site-isolation
You won't compromise security by enabling it - security is increased by enabling it. Because it's experimental it has a few bugs in some rare cases, the bugs are shown at the above link too, the bugs aren't security related. Here's the list of bugs I copied & pasted from the link above:
Higher memory use (about 10-20% when isolating all sites with many tabs open).
This overhead can be greatly reduced by only isolating certain sites, as noted below, and is expected to drop to about 10% in the heaviest cases in Chrome 64.
When printing a page, cross-site iframes appear blank.
To print the complete web page content, save the page locally, then open and print the saved file.
In some cases, clicking or scrolling on cross-site iframes may not work properly.
For example, this can happen when there is a partly transparent overlay above an iframe. (This is fixed in Chrome 65.)
When using the "Isolating all sites" approach below, Gmail may not load properly if started from the Gmail icon on chrome://apps.
To work around this, visit https://mail.google.com rather than using the Gmail icon on chrome://apps. (This is fixed in Chrome 64.)
Gmail Offline, Calendar Offline, and some other hosted apps may not work properly. (This is fixed in Chrome 64.)
I think it's worth leaving enabling Site Isolation, it goes above & beyond the Spectre/Meltdown fix.
I was wondering the same thing, as the message in the setting reads the feature is highly experimental and could in fact compromise security (?), and I've recently had trouble logging into some sites.
I've decided to disable it for now, as the new update is obviously already meant to take care of the issue.
I did some research just now and found the official in depth description of Strict Site Isolation from the people who developed the software: http://www.chromium.org/Home/chromium-security/site-isolation
You won't compromise security by enabling it - security is increased by enabling it. Because it's experimental it has a few bugs in some rare cases, the bugs are shown at the above link too, the bugs aren't security related. Here's the list of bugs I copied & pasted from the link above:
Higher memory use (about 10-20% when isolating all sites with many tabs open).
This overhead can be greatly reduced by only isolating certain sites, as noted below, and is expected to drop to about 10% in the heaviest cases in Chrome 64.
When printing a page, cross-site iframes appear blank.
To print the complete web page content, save the page locally, then open and print the saved file.
In some cases, clicking or scrolling on cross-site iframes may not work properly.
For example, this can happen when there is a partly transparent overlay above an iframe. (This is fixed in Chrome 65.)
When using the "Isolating all sites" approach below, Gmail may not load properly if started from the Gmail icon on chrome://apps.
To work around this, visit https://mail.google.com rather than using the Gmail icon on chrome://apps. (This is fixed in Chrome 64.)
Gmail Offline, Calendar Offline, and some other hosted apps may not work properly. (This is fixed in Chrome 64.)
I think it's worth leaving enabling Site Isolation, it goes above & beyond the Spectre/Meltdown fix.
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 1458
Joined: 2017-02-14
Love the mute tab idea.