![]() ![]() Security fixes impacting Stable channel then await the next Stable channel update once they have been backported. After the patch is landed, individuals across Chrome are working to test and verify the patch, and evaluate security bug fixes for backporting to affected release branches. ![]() The fix is then publicly accessible and discoverable. When a Chrome security bug is fixed, the fix is landed in the public Chromium source code repository. That’s why we believe it’s really important to ship security fixes as soon as possible, to minimize this “patch gap”. This exploitation of a known and patched security issue is referred to as n-day exploitation. This openness has benefits in testing fixes and discovering bugs, but comes at a cost: bad actors could possibly take advantage of the visibility into these fixes and develop exploits to apply against browser users who haven’t yet received the fix. Users of our Canary (and Beta) channels receive those fixes and can sometimes give us early warning of unexpected stability, compatibility, or performance problems in advance of the fix reaching the Stable channel. Anyone can view the source code, submit changes for review, and see the changes made by anyone else, even security bug fixes. This should not change how you use or update Chrome, nor is the frequency of milestone releases changing, but it does mean security fixes will get to you faster.Ĭhromium is the open source project which powers Chrome and many other browsers. Starting in Chrome 116, Stable updates will be released every week between milestones. We currently schedule one of these Stable channel updates (or “ Stable Refresh”) between each milestone. In between those major releases, we ship updates to address security and other high impact bugs. ![]() ![]() To get security fixes to you faster, starting now in Chrome 116, Chrome is shipping weekly Stable channel updates.Ĭhrome ships a new milestone release every four weeks. Posted by Amy Ressler, Chrome Security Team ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |