Saltar al contenido

Microsoft is synchronizing the release of the Chrome Cadence Edge

Microsoft is synchronizing the release of the Chrome Cadence Edge

It appears that Microsoft intends to update its Chromium-based Edge browser at about the same speed as Google is updating its Chrome browser.

Last week, Microsoft quietly updated its Chromium-based Edge to version 80, the first browser update since it debuted in a stable format three weeks earlier.

The Redmond, Washington company updated the Edge to version 80.0.361.48 on Friday, February 7, just three days after Google updated Chrome to version 80.

Chrome and Edge are each based on Chromium, the Google-dominated open source project responsible for creating and maintaining key browser technologies, including JavaScript and rendering engines. Chrome version 80 stone set at the beginning of December 2019

Since then, developers at Google and Microsoft have been working on their versions of Chromium 80, each using a multi-stage cadence of Canary, Dev, Beta and then Stable versions to release more progressive and reliable code.

One question that Microsoft has not addressed is how long it would take for it to switch from Chromium to a finished version of Edge, and more importantly, if there is a delay and, if so, how long will it take between the launch of Google Chrome and Microsoft Edge. The shorter the delay, the better: criminals could exploit a large gap by reverse engineering Chrome solutions to the security vulnerabilities in that version and then apply the results to an Edge that hasn’t been repaired yet.

The first Chrome security update since the release of Edge on January 15th was on January 16th. Microsoft released an update for the same vulnerabilities on January 17th. delay between Google’s promotion of a new version of Chrome to its stable affiliate and the next Microsoft example.

The value of the business as a service for storage media

On Tuesday, January 4, Google released Chrome 80.0.3987.87, with new features and 56 security fixes. Google has listed 37 of 56 CVE (Common Vulnerabilities and Exposures) identifiers. Ten of the 37 were rated «High», the second most serious rating in Chrome’s (and Chromium) four-step rating system.

In Microsoft’s Edge Security Recommendation, the company reported that Edge 80.0.361.48 also included fixes for the same 37 CVEs. (Microsoft probably fixed the 29 bugs for which Google did not include CVEs.)

What Microsoft hasn’t done yet is to describe what non-security changes Edge made between versions 79 and 80 (to be fair, Google didn’t do the same with Chrome 80, in part because it tends to feature new features and features when they reach the browser beta).

A comment on the support page titled «Release Notes for Microsoft Edge Security Updates,» for example, was ridiculously short, and at the request of Microsoft, it contacted Google Notes for Chrome 80.

Some ideas about Edge 80 changes can be found by searching the browser’s Group Policy documentation using the «version 80» string. In doing so, it was noticed that the Edge 80 will begin to apply the SameSite cookie control standard at about the same time as Chrome and will also address mixed content, especially by blocking file downloads over unencrypted connections, such as Chrome does. this thing.

Launching the Edge 80 close to Chrome also means that Edge 80 users should expect updates at the same pace as Chrome users with their browser and around the same data.

The following versions of Chrome are scheduled to be released on this date. Microsoft should update Edge in a few days.