Endpoint

9/27/2018
08:05 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Google to Let Users Disable Automatic Login to Chrome

The decision comes days after security researcher had blasted company for jeopardizing user privacy with browser update.

This story was updated on September 28 to clarify that with Chrome 70 Google will, by default, still automatically sign in users to Chrome when they sign in to a Google account, but users will get the option to disable the link.

Google has reversed course on a controversial recent browser update it introduced with little notice that automatically logs users in to Chrome whenever they sign in to any Google web account.

Starting with the next release of Chrome — Version 70 — Google is adding a control that gives users the choice of linking web-based sign-in with browser-based sign-in. Instead of automatically logging users in to Chrome when they sign in to a Gmail or other Google account, Chrome will let users decide if they want to be automatically signed in to the browser or not.

"For users that disable this feature, signing into a Google website will not sign them into Chrome," Chrome product manager Zach Koch announced in a blog post on September 26.

Importantly, though, the default setting in Chrome 70 will continue to be for users to get automatically signed in to Chrome when they log in to a Google account. What Google is making available with the next Chrome release is an option that lets users disable that setting, a Google spokeswoman clarified to Dark Reading Thursday. "Once the feature is disabled, it will stay disabled," the spokeswoman said.

The decision essentially restores the status that existed before Chrome 69, where users had the choice of keeping their sign-in to Google accounts completely separate from their sign-in for Chrome. A Gmail user concerned about Google collecting their browsing data, for instance, could use Chrome in basic browser mode without being signed in to it.

Google's change of heart comes days after security researcher Matthew Green from Johns Hopkins University had blasted the update in Chrome 69 as being sneaky and posing a substantial threat to user privacy. In a searing and widely quoted blog post, Green described the update as being unnecessary and deliberately putting users at risk of mistakenly allowing Google to collect their browsing data.

Google, meanwhile, described the update as harmless and providing a way to simplify the way Chrome handles logins. The company has maintained that when automatically signing users in to Chrome, it would only collect browsing data if a user explicitly consents to that collection.

Currently with Chrome 69, when a user signs into a Google account, his or her account picture or icon will appear in the Chrome user interface (UI). This enables the user to easily verify their sign-in status, according to Google. Signing out of Chrome will automatically log the user out of all their Google accounts.

In the Google blog post, Koch claimed that Google had introduced that update in response to feedback from users on shared devices who were confused about their sign-in state. "We think these UI changes help prevent users from inadvertently performing searches or navigating to websites that could be saved to a different user's synced account," he wrote.

Koch's post made no reference to the concerns raised by Green and others over the recent update. He merely noted that Google had heard "feedback" and was making changes to Chrome 70 to give users back the control they had over Chrome logins.

Google is also updating its Chrome UIs so users can more easily understand if their browsing data is being synced — or collected. "We want to be clearer about your sign-in state and whether or not you're syncing data to your Google Account," Koch wrote.

Related Content:

 

 

Black Hat Europe returns to London Dec. 3-6, 2018, with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
colad1930
50%
50%
colad1930,
User Rank: Strategist
9/28/2018 | 9:53:10 PM
Re: Yet another reason to use passwords on your device.
Good idea but Chrome is best for me. 

 

With this update, I think Google will fix the new unwanted things.

 

Let's see what comes out of the update next month.
ANON1251724318124
50%
50%
ANON1251724318124,
User Rank: Apprentice
9/28/2018 | 5:06:53 PM
Yet another reason to use passwords on your device.
If you use passwords to access your windows account, cell phone table etc, then the only way you will lose control of your automatic google chrome login is to lose your device.  

 

Always use some form of authenication for every computer device used to transmit or update personal information.   Stop using chrome browswer if you like.   There aare other browsers.

 
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
New Free Tool Scans for Chrome Extension Safety
Dark Reading Staff 2/21/2019
Privacy Ops: The New Nexus for CISOs & DPOs
Amit Ashbel, Security Evangelist, Cognigo,  2/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8955
PUBLISHED: 2019-02-21
In Tor before 0.3.3.12, 0.3.4.x before 0.3.4.11, 0.3.5.x before 0.3.5.8, and 0.4.x before 0.4.0.2-alpha, remote denial of service against Tor clients and relays can occur via memory exhaustion in the KIST cell scheduler.
CVE-2019-1698
PUBLISHED: 2019-02-21
A vulnerability in the web-based user interface of Cisco Internet of Things Field Network Director (IoT-FND) Software could allow an authenticated, remote attacker to gain read access to information that is stored on an affected system. The vulnerability is due to improper handling of XML External E...
CVE-2019-1700
PUBLISHED: 2019-02-21
A vulnerability in field-programmable gate array (FPGA) ingress buffer management for the Cisco Firepower 9000 Series with the Cisco Firepower 2-port 100G double-width network module (PID: FPR9K-DNM-2X100G) could allow an unauthenticated, adjacent attacker to cause a denial of service (DoS) conditio...
CVE-2019-6340
PUBLISHED: 2019-02-21
Some field types do not properly sanitize data from non-form sources in Drupal 8.5.x before 8.5.11 and Drupal 8.6.x before 8.6.10. This can lead to arbitrary PHP code execution in some cases. A site is only affected by this if one of the following conditions is met: The site has the Drupal 8 core RE...
CVE-2019-8996
PUBLISHED: 2019-02-21
In Signiant Manager+Agents before 13.5, the implementation of the set command has a Buffer Overflow.