![]() ANGLE, Web Audio, Brotli) and we’ve begun making contributions to the Chromium project to help move browsing forward on new ARM-based Windows devices. We’ve also used open source for various features of Microsoft Edge on the desktop (e.g. Our new mobile browser has been based on open source from its beginnings over a year ago. Working with open source is not new for Microsoft Edge. And of course, we and all those audiences care primarily about the end-user, who is ultimately the audience this work is intended to benefit. The audiences we think will find this document most relevant and useful are (a) the people working on Chromium as approvers/maintainers and leading that project (b) the companies and engineers who build other browsers and will be interested in the contributions we plan to make, and (c) the broader community of web developers, corporate IT managers and partners we work with on Windows and Microsoft Edge. This document exists to clarify our thinking on how that work will proceed: we want to explain our plans and intentions related to Microsoft Edge and the Chromium open-source project. We are starting down a path to adopt Chromium open source in the development of Microsoft Edge on the desktop, becoming a larger contributor and user of its open source so that we can create better web compatibility for our customers and less fragmentation of the web for all web developers. Microsoft Edge and Chromium Open Source: Our Intentįor the past few years, Microsoft has meaningfully increased participation in the open source software (OSS) community, becoming one of the world’s largest supporters of OSS projects. Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL. Various fixes from internal audits, fuzzing and other initiatives We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.Īs usual, our ongoing internal security work was responsible for a wide range of fixes: High CVE-2023-5472: Use after free in Profiles. Please see the Chrome Security Page for more information. Below, we highlight fixes that were contributed by external researchers. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. ![]() The Extended Stable channel has been updated to 1.117 for Mac and 1.118 for Windows, which will roll out over the coming days/weeks. A full list of changes in this build is available in the log. ![]() The Stable channel has been updated to 1.117 for Mac and Linux and 1.117/.118 for Windows, which will roll out over the coming days/weeks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |