Chrome 69, released earlier this month, is a major overhaul of Google\u2019s web browser. It offers a sleek new look and a host of new features including a revamped password manager and a \u201csmart answer\u201d tool.<\/b>
\nChrome 69, released earlier this month, is a major overhaul of Google\u2019s web browser. It offers a sleek new look and a host of new features including a revamped password manager and a \u201csmart answer\u201d tool.
Another feature added to Chrome is automatic login. Whenever you log into a Google website like Gmail or YouTube, Chrome 69 will automatically sign you into the browser. At first glance, it seems an easy and quick way to utilize Chrome\u2019s personalization features, but it is more intrusive than helpful according to security researchers.
For one thing, it removes the ability for the user to choose whether or not he or she wants to log into the browser. Forcing users to browse logged in is bad form no matter how helpful the function is perceived to be, but security experts say that it goes beyond that and is a violation of your privacy.
Professor of Cryptography Matthew Green at John Hopkins University says that the feature has completely turned him off of using Chrome, which he says he once loved.
\u201cFor many years, Google offered an optional \u2018sign in\u2019 feature for Chrome, which presumably vacuumed up your browsing data and shipped it off to Google, but that was an option,\u201d said Green in his blog . \u201c[Now] Chrome will automatically sign the browser into your Google account for you. It\u2019ll do this without asking, or even explicitly notifying you.\u201d
Green called the developers out on Twitter, but the company defended the move saying that it’s more like a «FYI» notification than actually signing in. No, really, they did.
Think of it as adding «yo FYI you’re currently logged in to Gmail» in the corner of the browser window. That’s what the feature does. It’s different from the feature you seem to be talking about which we call sync, that has privacy implications.
\u2014 Adrienne Porter Felt (@__apf__) September 22,2018
Green notes that developers are saying that this auto login will not sync your data with Google servers \u2014 at least not yet. You still have to opt-in to the service for syncing to occur. However, Green takes issue with Google\u2019s rationale for the feature.
Devs are concerned about what happens when Chrome is signed into one account, but then a different user logs into a Google-based website to say, check his or her email on the same computer. Presumably, account A will end up syncing account B\u2019s data. This concern is legitimate.
However, Green notes that the precautionary measure only pertains to users who prefer logging into Chrome. It does not apply to those who would rather browse logged out. To put it another way, all users are being forced to sign into Chrome when they access Google sites because the devs cannot figure out a way to keep data from two accounts separate.
Green is not alone in his misgivings. Cloudflare CTO John Graham-Cumming and Intel security expert Ryan Naraine voiced their concerns and said they would be switching browsers.
Sadly I noticed I\u2019m logged in to Chrome on my work account. Moving over to Firefox this morning. I agree about the \u201cdark pattern\u201d on the Sync \u201cbutton\u201d. https:\/\/t.co\/jO7k1KrktP
\u2014 John Graham-Cumming (@jgrahamc) September 24,2018
\u201cThe Chrome guys get a lot right. This isn\u2019t one of them,\u201d Naraine said on Twitter.
Attempting to keep user data separate on a shared computer is a valid concern. It is Google’s approach to the problem that failed. Not giving the user a choice in the matter is the wrong way to go regardless of whether or not data collection is occurring.<\/p>\n

\n

Similarity rank: 5.3<\/div>\n

Sentiment rank: 1.5<\/div>\n

<\/div>\n<\/div>\n