News: 1589957709

Google released Chrome 83 on Tuesday after skipping version 82 entirely due to coronavirus-related challenges, bringing with it security for DNS queries, a revised extension interface that developers dislike, and a few other features.

The latest iteration of Google's browser implements DNS-over-HTTPS (DoH), a way to prevent domain-name queries from being observed on the network, between the browser and the DNS server, at least. Traditionally, DNS queries and replies sent using TCP or UDP are not encrypted, even when internet users are interacting with websites over an encrypted HTTPS connection.

DoH was proposed to improve privacy and security by wrapping TLS encryption around the DNS queries that convert human-friendly domain names, like theregister.co.uk, into network addresses computers can connect to, such as 104.18.5.22.

Google has been testing DoH [1]since Chrome 78 last year, and is now rolling it out proper. Mozilla has been doing the same in its Firefox browser, and in February made DoH available [2]to US Firefox users by default.

Not all smiles and sunshine

The technology remains controversial because some people and organizations expect or demand less privacy in certain scenarios.

Paul Vixie, CEO of Farsight Security and developer of several DNS protocol extensions, has [3]argued for DNS-over-TLS (DoT), an alternative query protection protocol because it can be blocked by firewalls and controlled by systems administrators.

Cloudflare [4]contends DoT is better from a network security perspective while DoH is better from a privacy perspective. The fact DoH provides corporate IT administrators with less visibility into network traffic isn't ideal when oversight is desired, it noted.

It's also not ideal for business models that benefit from network traffic snooping. Last summer, the UK Internet Services Providers’ Association nominated Mozilla as the internet's [5]2019 villain of the year due to concerns its DoH implementation would bypass British internet filters and parental controls. Though the trade group backtracked, both Mozilla and Google have had to convince lawmakers in the US and UK that DNS privacy won't lead to the unrestrained transmission and receipt of unlawful content.

DNS-over-HTTPS primarily stops ISPs and others on the network path snooping on DNS queries to hit subscribers with targeted ads based on the sites they've visited, though it has other benefits. For instance, it stops miscreants on the network path silently tampering with domain query results to redirect people to password-stealing imitation websites, or unexpectedly blocking look-ups. It also reassures the browser it is speaking to the DNS server it was expecting.

Enterprise excepted that is

Aware of the needs of corporate network administrators to have visibility on their users' activities, Kenji Baheux, Chrome product manager, said in a [6]blog post that Chrome will disable DoH in managed environments that declare relevant enterprise policies.

Microsoft joins Google and Mozilla in adopting DNS-over-HTTPS data security protocol [7]READ MORE

"We’ve also added new DNS-over-HTTPS enterprise policies to allow for a managed configuration of Secure DNS and encourage IT administrators to look into deploying DNS-over-HTTPS for their users," said Baheux. "We believe that our approach strikes a good balance between moving security and privacy forward and maintaining user expectations."

Chrome 83, initially available for Chrome OS, Windows and macOS, with Android and Linux updates coming soon, will automatically activate DoH if the user's current ISP supports it. Users can also configure a secure DNS provider in the Advanced security menu, or disable it completely.

Google's Chrome developers have reworked various browser Privacy and Security settings menus, to make cookie management and sensitive permissions like location, camera, and microphone access more easily accessible. Finally, Incognito mode will block third-party cookies by default.

Also, the “Clear browsing data” control has been moved to the top of the Privacy & Security settings menu "because many people regularly delete their browsing history," explained senior product manager AbdelKarim Mardini in a [8]blog post .

A Safety check section has been added so that Chrome users can click the "Check now" button to see if any of their Chrome-stored passwords have shown up in Google's database of publicly exposed credentials.

Google's extension issues

The browser also supposedly checks for compromised extensions, presumably those flagged by Google after days or months of misbehavior – the Chrome Web Store [9]hasn't been known for catching malicious extensions before they can do harm, though that's a goal of the company's ever tightening developer rules and [10]Manifest v3 API hobbling .

The update adds a new puzzle icon in the Chrome toolbar to access a reworked extensions menu. "It’s a neat way to tidy up your toolbar, and gives you more control over what data extensions can access on sites you visit," said Mardini. "With this addition, you’ll still be able to pin your favorite extensions to the toolbar."

But Chrome no longer pins extensions to the toolbar by default, a change of convention that hasn't gone over well with Chrome extension developers. When Google initially discussed the revised extension management interface, those making extensions [11]objected because requiring users to take action to pin an extension so it's always visible makes interaction less likely.

Last week, Chrome extension developer advocate Simeon Vincent acknowledged that concern and said Google would do nothing to accommodate it.

"Many commenters have expressed reservations about action buttons being unpinned by default," he wrote in [12]a forum post .

"We understand this concern. An extension's action in the toolbar is an important interaction mechanism, and we don't intend to decrease extension usage. However, after several discussions and lengthy consideration, we think that leaving actions unpinned by default is the best course for our longer-term plans for the Chrome extension platform."

That left extension developers [13]grumbling that Google never had any intention of testing the feature or incorporating developer feedback. ®



[1] https://www.theregister.co.uk/2019/09/10/chrome_78_dnsoverhttps/

[2] https://www.theregister.co.uk/2020/02/25/mozilla_turns_on_dns_over_https_by_default_for_usa/

[3] https://twitter.com/paulvixie/status/1171154286316679168?s=20

[4] https://www.cloudflare.com/learning/dns/dns-over-tls/

[5] https://www.theregister.co.uk/2019/07/06/mozilla_ukisp_vallain/

[6] https://blog.chromium.org/2020/05/a-safer-and-more-private-browsing-DoH.html

[7] https://www.theregister.co.uk/2019/11/19/microsoft_joins_doh/

[8] https://blog.google/products/chrome/more-intuitive-privacy-and-security-controls-chrome/

[9] https://www.theregister.co.uk/2020/04/15/google_malicious_chrome/

[10] https://www.theregister.co.uk/2019/06/17/chrome_extensions_security/

[11] https://www.theregister.co.uk/2020/04/07/chrome_hiding_extensions/

[12] https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/rOso__zU_sM/UTxbb5gnAgAJ

[13] https://groups.google.com/a/chromium.org/d/msg/chromium-extensions/rOso__zU_sM/399FrnlaAAAJ