Slashdot Mirror
Google Chrome 67 Released for Windows, Mac, and Linux (bleepingcomputer.com)
An anonymous reader shares a report: Google released earlier today Chrome 67, the latest stable release of its web browser. According to changelogs released with Chrome 67, this version adds support for a Generic Sensors API, improves AR and VR experiences, and deprecates the HTTP-Based Public Key Pinning (HPKP) security feature. Probably the biggest change in Chrome 67 is the addition of the Generic Sensors API. As the name implies, this is an API that exposes data from device sensors to public websites. The new API is based on the Generic Sensor W3C standard. This API is meant primarily for mobile use, and in its current version, websites can use Chrome's Generic Sensors API to access data from a device's accelerometer, gyroscope, orientation and motion sensors. Another API that shipped with Chrome is the WebXR Device API. Developers can use this API to build virtual and augmented reality experiences on Chrome for mobile-based VR headsets like Google Daydream View and Samsung Gear VR, as well as desktop-hosted headsets like Oculus Rift, HTC Vive, and Windows Mixed Reality Headsets.
On Windows, if you have UAC enabled, you'll be asked if you want to let the installer elevate. But if you say "no" on that prompt, it will install without creating system services (since the installer never received the privilege escalation to do so). This is also how non-admins can install it on a per-user basis.
Virtual reality? It's a web browser, not Emacs.
Table-ized A.I.
Comment removed based on user account deletion
For a long period of time Google was exploiting vulnerabilities to install Chrome with admin privileges despite the user not having admin privileges or not granting them to the installation process.
Certificate transparency = distributed HPKP
HPKP allows the operator to declare this certificate or bust to regular users. Certificate transparency offers no such capability.
Certificate transparency only provides "transparency". It doesn't allow operators to set declarative limits on what is acceptable.
If your website was gearing up for protest against local dictator and chief and they conspired against you obtaining a MITM cert from your CA and properly logged it to transparency log accordingly that information sure as hell won't do your users any good who are now being rounded up thanks to this ridiculous assertion of equivalence.
Certificate transparency *IS* a good thing and it is worth doing yet value offered by each approach does not fully overlap. Removal of HPKP only reduces security. It does not improve it.
Does Google Chrome browser still install system services? If so, I would never use it.
Or you could educate yourself on what it means to have a system service vs a normal program, what they do, and why they run as a service. But no ignorance is far easier.
What about in Mac OS with its annoying background self updater?
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).